 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| features ? high performance, low power avr ? 8-bit microcontroller ? advanced risc architecture ? 120 powerful instructions ? most single clock cycle execution ? 32 x 8 general purpose working registers ? fully static operation ? up to 20 mips throughput at 20 mhz ? data and non-volatile program and data memories ? 2/4k bytes of in-system self programmable flash ? endurance 10,000 write/erase cycles ? 128/256 bytes in-system programmable eeprom ? endurance: 100,000 write/erase cycles ? 128/256 bytes internal sram ? programming lock fo r flash program and eeprom data security ? peripheral features ? one 8-bit timer/counter with se parate prescaler and compare mode ? one 16-bit timer/counter with separate prescaler, compare and capture modes ?four pwm channels ? on-chip analog comparator ? programmable watchdog timer with on-chip oscillator ? usi ? universal serial interface ? full duplex usart ? special microcontroller features ? debugwire on-chip debugging ? in-system programmable via spi port ? external and internal interrupt sources ? low-power idle, power-down, and standby modes ? enhanced power-on reset circuit ? programmable brown-out detection circuit ? internal calibrated oscillator ? i/o and packages ? 18 programmable i/o lines ? 20-pin pdip, 20-pin soic, 20-pad mlf/vqfn ? operating voltage ? 1.8 ? 5.5v ? speed grades ? 0 ? 4 mhz @ 1.8 ? 5.5v ? 0 ? 10 mhz @ 2.7 ? 5.5v ? 0 ? 20 mhz @ 4.5 ? 5.5v ? industrial temperature range: -40 c to +85 c ? low power consumption ? active mode ? 190 a at 1.8v and 1mhz ?idle mode ? 24 a at 1.8v and 1mhz ? power-down mode ? 0.1 a at 1.8v and +25 c 8-bit microcontroller with 2/4k bytes in-system programmable flash attiny2313a attiny4313 rev. 8246b?avr?09/11
2 8246b?avr?09/11 attiny2313a/4313 1. pin configurations figure 1-1. pinout attiny2313a/4313 (pcint10/reset/dw) pa2 (pcint11/rxd) pd0 (pcint12/txd) pd1 (pcint9/xtal2) pa1 (pcint8/clki/xtal1) pa0 (pcint13/ckout/xck/int0) pd2 (pcint14/int1) pd3 (pcint15/t0) pd4 (pcint16/oc0b/t1) pd5 gnd 20 19 18 17 16 15 14 13 12 11 1 2 3 4 5 6 7 8 9 10 vcc pb7 (usck/scl/sck/pcint7) pb6 (miso/do/pcint6) pb5 (mosi/di/sda/pcint5) pb4 (oc1b/pcint4) pb3 (oc1a/pcint3) pb2 (oc0a/pcint2) pb1 (ain1/pcint1) pb0 (ain0/pcint0) pd6 (icpi/pcint17) pdip/soic 1 2 3 4 5 mlf/vqfn 15 14 13 12 11 20 19 18 17 16 6 7 8 9 10 (pcint12/txd) pd1 (pcint9/xtal2) pa1 (pcint8/clki/xtal1) pa0 (pcint13/ckout/xck/int0) pd2 (pcint14/int1) pd3 (pcint15/t0) pd4 (pcint16/oc0b/t1) pd5 gnd (pcint17/icpi) pd6 (ain0/pcint0) pb0 pb5 (mosi/di/sda/pcint5) pb4 (oc1b/pcint4) pb3 (oc1a/pcint3) pb2 (oc0a/pcint2) pb1 (ain1/pcint1) pd0 (rxd/pcint11) pa2 (reset/dw/pcint10) vcc pb7 (usck/scl/sck/pcint7) pb6 (miso/do/pcint6) note: bottom pad should be soldered to ground. 3 8246b?avr?09/11 attiny2313a/4313 1.1 pin descriptions 1.1.1 vcc digital supply voltage. 1.1.2 gnd ground. 1.1.3 port a (pa2..pa0) port a is a 3-bit bi-directional i/o port with inte rnal pull-up resistors (selected for each bit). the port a output buffers have symmetrical drive characteristics with both high sink and source capability, except pa2 which has the reset capability. to use pin pa2 as i/o pin, instead of reset pin, program (?0?) rstdisbl fuse. as input s, port a pins that are externally pulled low will source current if the pull-up resistors are activated. the port a pins are tri-stated when a reset condition becomes active, even if the clock is not running. port a also serves the functions of various special features of the attiny2313a/4313 as listed on page 62 . 1.1.4 port b (pb7..pb0) port b is an 8-bit bi-directional i/o port with internal pull-up resistors (selected for each bit). the port b output buffers have symmetrical drive characteristics with both high sink and source capability. as inputs, port b pi ns that are externally pulled low will source current if the pull-up resistors are activated. the port b pins are tri-stated when a reset condition becomes active, even if the clock is not running. port b also serves the functions of various special features of the attiny2313a/4313 as listed on page 63 . 1.1.5 port d (pd6..pd0) port d is a 7-bit bi-directional i/o port with inte rnal pull-up resistors (selected for each bit). the port d output buffers have symmetrical drive c haracteristics with bot h high sink and source capability. as inputs, port d pi ns that are externally pulled lo w will source current if the pull-up resistors are activated. the port d pins are tri-stated when a reset condition becomes active, even if the clock is not running. port d also serves the functions of various special features of the attiny2313a/4313 as listed on page 67 . 1.1.6 reset reset input. a low level on this pin for longer than the minimum pulse length will generate a reset, even if the clock is not running and provided that the reset pin has not been disabled. the minimum pulse length is given in table 22-3 on page 201 . shorter pulses are not guaranteed to generate a reset. the reset input is an alternate function for pa2 and dw. the reset pin can also be used as a (weak) i/o pin. 1.1.7 xtal1 input to the inverting oscillator amplifier and input to the internal clock operating circuit. xtal1 is an alternate function for pa0. 4 8246b?avr?09/11 attiny2313a/4313 1.1.8 xtal2 output from the inverting osc illator amplifier. xtal2 is an alternate function for pa1. 5 8246b?avr?09/11 attiny2313a/4313 2. overview the attiny2313a/4313 is a low-power cmos 8- bit microcontroller based on the avr enhanced risc architecture. by executing powerful instructions in a single clock cycle, the attiny2313a/4313 achieves throughputs approach ing 1 mips per mhz allowing the system designer to optimize power consum ption versus processing speed. 2.1 block diagram figure 2-1. block diagram program counter program flash instruction register gnd vcc instruction decoder control lines stack pointer sram general purpose register alu status register programming logic spi 8-bit data bus xtal1 xtal2 reset internal oscillator oscillator watchdog timer timing and control mcu control register mcu status register timer/ counters interrupt unit eeprom usi usart analog comparator data register portb data dir. reg. portb data register porta data dir. reg. porta portb drivers pb0 - pb7 porta drivers pa0 - pa2 data register portd data dir. reg. portd portd drivers pd0 - pd6 on-chip debugger internal calibrated oscillator 6 8246b?avr?09/11 attiny2313a/4313 the avr core combines a rich instruction set with 32 general purpose working registers. all the 32 registers are directly connected to the arithmetic logic unit (alu), allowing two independent registers to be accessed in one single instruction executed in one clock cycle. the resulting architecture is more code efficient while achiev ing throughputs up to ten times faster than con- ventional cisc microcontrollers. the attiny2313a/4313 provides the following features: 2/4k bytes of in-system programmable flash, 128/256 bytes eeprom, 12 8/256 bytes sram, 18 general pu rpose i/o lines, 32 general purpose working registers, a single-wire interface for on-chip debugging, two flexible timer/counters with compare modes, internal and external interrupts, a serial programmable usart, universal serial interface with start condition detector, a programmable watchdog timer with internal oscillator, an d three software selectable powe r saving modes. the idle mode stops the cpu while allowing the sram, timer/counters, and interrupt system to continue func- tioning. the power-down mode saves the register contents but freezes th e oscillator, disabling all other chip functions until the next interrupt or hardware reset. in standby mode, the crys- tal/resonator oscillator is running while the rest of the device is sleeping. this allows very fast start-up combined with low-power consumption. the device is manufactured using atmel?s high density non-volatile memory technology. the on-chip isp flash allows the program memory to be reprogrammed in-system through an spi serial interface, or by a conventional non-vol atile memory programmer. by combining an 8-bit risc cpu with in-system self-programmable flash on a monolithic chip, the atmel attiny2313a/4313 is a powerful microcontroller that provides a highly flexible and cost effective solution to many embedded control applications. the attiny2313a/4313 avr is supported with a full suite of program and system development tools including: c compilers, macro assemblers, program debugger/simulators, in-circuit emu- lators, and evaluation kits. 2.2 comparison between at tiny2313a and attiny4313 the attiny2313a and attiny4313 differ only in memory sizes. table 2-1 summarizes the differ- ent memory sizes for the two devices. table 2-1. memory size summary device flash eeprom ram attiny2313a 2k bytes 128 bytes 128 bytes attiny4313 4k bytes 256 bytes 256 bytes 7 8246b?avr?09/11 attiny2313a/4313 3. about 3.1 resources a comprehensive set of drivers, application notes, data sheets and descriptions on development tools are available for download at http://www.atmel.com/avr. 3.2 code examples this documentation contains simple code examples that briefly show how to use various parts of the device. these code examples assume that the part specific header file is included before compilation. be aware that not all c compiler vendors include bit definitions in the header files and interrupt handling in c is compiler dependent. please confirm with the c compiler documen- tation for more details. for i/o registers located in the extended i/o map, ?in?, ?out?, ?sbis?, ?sbic?, ?cbi?, and ?sbi? instructions must be replaced with instructions that allow access to extended i/o. typically, this means ?lds? and ?sts? combined with ?sbrs?, ?s brc?, ?sbr?, and ?cbr?. note that not all avr devices include an extended i/o map. 3.3 data retention reliability qualification results show that the pr ojected data retention failure rate is much less than 1 ppm over 20 years at 85c or 100 years at 25c. 8 8246b?avr?09/11 attiny2313a/4313 4. cpu core this section discusses the avr core architecture in general. the main function of the cpu core is to ensure correct program execution. the cpu must therefore be able to access memories, perform calculations, control peripherals, and handle interrupts. 4.1 architectural overview figure 4-1. block diagram of the avr architecture in order to maximize performance and parallelism, the avr uses a harvard architecture ? with separate memories and buses for program and data. instructions in the program memory are executed with a single level pipelining. while one instruction is being executed, the next instruc- tion is pre-fetched from the program memory. this concept enables instructions to be executed in every clock cycle. the program memory is in-system reprogrammable flash memory. the fast-access register file contains 32 x 8-bit general purpose working registers with a single clock cycle access time. this allows single-cycle ar ithmetic logic unit (alu ) operation. in a typ- ical alu operation, two operands are output from the register file, the operation is executed, and the result is stored back in the register file ? in one clock cycle. flash program memory instruction register instruction decoder program counter control lines 32 x 8 general purpose registrers alu status and control i/o lines eeprom data bus 8-bit data sram direct addressing indirect addressing interrupt unit spi unit watchdog timer analog comparator i/o module 2 i/o module1 i/o module n 9 8246b?avr?09/11 attiny2313a/4313 six of the 32 registers can be used as three 16-b it indirect address register pointers for data space addressing ? enabling efficient address calculations. one of the these address pointers can also be used as an address pointer for look up tables in flash program memory. these added function registers are the 16-bit x-, y-, and z-register, described later in this section. the alu supports arithmetic and logic operations between registers or between a constant and a register. single register operations can also be executed in the alu. after an arithmetic opera- tion, the status register is updated to reflect information about the result of the operation. program flow is provided by conditional and uncon ditional jump and call instructions, able to directly address the whole address space. most avr instructions have a single 16-bit word for- mat. every program memory address contains a 16- or 32-bit instruction. during interrupts and subroutine calls, the return address program counter (pc) is stored on the stack. the stack is effectively allocated in the general data sram, and consequently the stack size is only limited by the to tal sram size and the usage of the sram. all user programs must initialize the sp in the reset routine (before subroutines or interrupts are executed). the stack pointer (sp) is read/write accessible in the i/o space. the data sram can easily be accessed through the five different addressing modes supported in the avr architecture. the memory spaces in the avr architecture are all linear and regular memory maps. a flexible interrupt module has its control r egisters in the i/o space with an additional global interrupt enable bit in the status register. all interrupts have a separate interrupt vector in the interrupt vector table. the interrupts have priority in accordance with their interrupt vector posi- tion. the lower the interrupt vector address, the higher the priority. the i/o memory space contains 64 addresses for cpu peripheral functi ons as control regis- ters, and other i/o functions. the i/o memory can be accessed directly, or as the data space locations following those of the register file, 0x20 - 0x5f. 4.2 alu ? arithm etic logic unit the high-performance avr alu operates in dire ct connection with all the 32 general purpose working registers. within a single clock cycle, arithmetic operations between general purpose registers or between a register and an immediate are executed. the alu operations are divided into three main categories ? arithmetic, logical, and bit-functions. some implementations of the architecture also provide a powerful multiplier supporting both signed/unsigned multiplication and fractional format. see the ?instruction set? section for a detailed description. 4.3 status register the status register contains information about the result of the most recently executed arithme- tic instruction. this information can be used for altering program flow in order to perform conditional operations. note that the status register is updated after all alu operations, as specified in the instruction set reference. this will in many cases remove the need for using the dedicated compare instructions, resulting in faster and more compact code. the status register is not automatically stored when entering an interrupt routine and restored when returning from an interrupt. this must be handled by software. 10 8246b?avr?09/11 attiny2313a/4313 the avr status register ? sreg ? is defined as: ? bit 7 ? i: global interrupt enable the global interrupt enable bit must be set for th e interrupts to be enabled. the individual inter- rupt enable control is then performed in separate control registers. if the global interrupt enable register is cleared, none of the interrupts are enabled independent of the individual interrupt enable settings. the i-bit is cleared by hardware after an interrupt has occurred, and is set by the reti instruction to enable subsequent interrupts. the i-bit can also be set and cleared by the application with the sei and cli instructions, as described in the instruction set reference. ? bit 6 ? t: bit copy storage the bit copy instructions bld (bit load) and bst (b it store) use the t-bit as source or desti- nation for the operated bit. a bit from a register in the register file can be copied into t by the bst instruction, and a bit in t can be copied into a bit in a register in the register file by the bld instruction. ? bit 5 ? h: half carry flag the half carry flag h indicates a half carry in so me arithmetic operations. half carry is useful in bcd arithmetic. see the ?instruction set description? for detailed information. ? bit 4 ? s: sign bit, s = n v the s-bit is always an exclusive or between the negative flag n and the two?s complement overflow flag v. see the ?instruction set description? for detailed information. ? bit 3 ? v: two?s complement overflow flag the two?s complement overflow flag v suppor ts two?s complement arithmetics. see the ?instruction set description? for detailed information. ? bit 2 ? n: negative flag the negative flag n indicates a negative result in an arithmetic or logic operation. see the ?instruction set description? for detailed information. ? bit 1 ? z: zero flag the zero flag z indicates a zero result in an arithmetic or logic operation. see the ?instruction set description? for detailed information. ? bit 0 ? c: carry flag the carry flag c indicates a carry in an arithmetic or logic operation. see the ?instruction set description? for de tailed information. bit 76543210 0x3f (0x5f) i t h s v n z c sreg read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 11 8246b?avr?09/11 attiny2313a/4313 4.4 general purpose register file the register file is optimized for the avr enhanc ed risc instruction set. in order to achieve the required performance and flex ibility, the following in put/output schemes ar e supported by the register file: ? one 8-bit output operand and one 8-bit result input ? two 8-bit output operands and one 8-bit result input ? two 8-bit output operands and one 16-bit result input ? one 16-bit output operand and one 16-bit result input figure 4-2 shows the structure of the 32 general purpose working registers in the cpu. figure 4-2. avr cpu general purpose working registers most of the instructions operating on the register file have direct access to all registers, and most of them are single cycle instructions. as shown in figure 4-2 , each register is also assigned a data memory address, mapping them directly into the first 32 locations of the user data space. although not being physically imple- mented as sram locations, this memory organization provides great flexibility in access of the registers, as the x-, y- and z-pointer registers can be set to index any register in the file. 4.4.1 the x-register, y-register, and z-register the registers r26..r31 have some added functions to their general purpose usage. these reg- isters are 16-bit address pointers for indirect addressing of the data space. the three indirect address registers x, y, and z are defined as described in figure 4-3 . 7 0 addr. r0 0x00 r1 0x01 r2 0x02 ? r13 0x0d general r14 0x0e purpose r15 0x0f working r16 0x10 registers r17 0x11 ? r26 0x1a x-register low byte r27 0x1b x-register high byte r28 0x1c y-register low byte r29 0x1d y-register high byte r30 0x1e z-register low byte r31 0x1f z-register high byte 12 8246b?avr?09/11 attiny2313a/4313 figure 4-3. the x-, y-, and z-registers in the different addressing modes these address registers have functions as fixed displacement, automatic increment, and automatic decrement (see the instruction set reference for details). 4.5 stack pointer the stack is mainly used for storing temporary data, for storing local variables and for storing return addresses after interrupts and subroutine calls. the stack pointer register always points to the top of the stack. note that the stack is implemented as growing from higher memory loca- tions to lower memory locations. this implies that a stack push command decreases the stack pointer. the stack pointer points to the data sram stack area where the subroutine and interrupt stacks are located. this stack space in the data sram must be defined by the program before any subroutine calls are executed or interrupts are enabled. the stack pointer must be set to point above 0x60. the stack pointer is decrement ed by one when data is pushed onto the stack with the push instruction, and it is decremented by two when the return address is pushed onto the stack with subroutine call or interrupt. the stack pointer is incremented by one when data is popped from the stack with the pop instruction, and it is incremented by two when data is popped from the stack with return from subroutine ret or return from interrupt reti. the stack pointer is implemented as one 8-bit register in the i/o space. 4.6 instruction execution timing this section describes the general access timi ng concepts for instruction execution. the avr cpu is driven by the cpu clock clk cpu , directly generated from the selected clock source for the chip. no internal clo ck division is used. figure 4-4 shows the parallel instruction fetches and instruction executions enabled by the har- vard architecture and the fast-access register file concept. this is the basic pipelining concept to obtain up to 1 mips per mhz with the corr esponding unique results for functions per cost, functions per clocks, and functions per power-unit. 15 xh xl 0 x-register 707 0 r27 (0x1b) r26 (0x1a) 15 yh yl 0 y-register 707 0 r29 (0x1d) r28 (0x1c) 15 zh zl 0 z-register 70 7 0 r31 (0x1f) r30 (0x1e) bit 76543210 0x3d (0x5d) sp7 sp6 sp5 sp4 sp3 sp2 sp1 sp0 spl read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value ramend ramend rame nd ramend ramend ra mend ramend ramend 13 8246b?avr?09/11 attiny2313a/4313 figure 4-4. the parallel instruction fetches and instruction executions figure 4-5 shows the internal timing concept for the register file. in a single clock cycle an alu operation using two register operands is executed, and the result is stored back to the destina- tion register. figure 4-5. single cycle alu operation 4.7 reset and inte rrupt handling the avr provides several different interrupt sources. these interrupts and the separate reset vector each have a separate program vector in the program memory space. all interrupts are assigned individual enable bits which must be written logic one together with the global interrupt enable bit in the status register in order to enable the interrupt. the lowest addresses in the program memory space are by default defined as the reset and interrupt vectors. the complete list of vectors is shown in ?interrupts? on page 48 . the list also determines the priority levels of the different interrupts. the lower the address the higher is the priority level. reset has the highest priority, and next is int0 ? the external interrupt request 0. refer to ?interrupts? on page 48 for more information. when an interrupt occurs, the global interrupt enable i-bit is cleared and all interrupts are dis- abled. the user software can write logic one to the i-bit to enable nested interrupts. all enabled interrupts can then interrupt the current interrupt routine. the i-bit is automatically set when a return from interrupt instruction ? reti ? is executed. there are basically two types of interrupts. the fi rst type is triggered by an event that sets the interrupt flag. for these interrupts, the program counter is vectored to the actual interrupt vector in order to execute the interrupt handling rout ine, and hardware clears the corresponding inter- rupt flag. interrupt flags can also be cleared by wr iting a logic one to the flag bit position(s) to be clk 1st instruction fetch 1st instruction execute 2nd instruction fetch 2nd instruction execute 3rd instruction fetch 3rd instruction execute 4th instruction fetch t1 t2 t3 t4 cpu total execution time register operands fetch alu operation execute result write back t1 t2 t3 t4 clk cpu 14 8246b?avr?09/11 attiny2313a/4313 cleared. if an interrupt condition occurs while the corresponding interrupt enable bit is cleared, the interrupt flag will be set and re membered until the inte rrupt is enabled, or the flag is cleared by software. similarly, if one or more interrupt condit ions occur while the global interrupt enable bit is cleared, the corresponding interrupt flag(s) w ill be set and remembered until the global interrupt enable bit is set, and will th en be executed by order of priority. the second type of interrupts will trigger as long as the interrupt condition is present. these interrupts do not necessarily have interrupt flags. if the interrupt condition disappears before the interrupt is enabled, the in terrupt will not be triggered. when the avr exits from an inte rrupt, it will always retu rn to the main pr ogram and execute one more instruction before any pending interrupt is served. note that the status register is not automatica lly stored when entering an interrupt routine, nor restored when returning from an interrupt routine. this must be handled by software. when using the cli instruction to disable interrupts, the interrup ts will be immediately disabled. no interrupt will be executed af ter the cli instruction, even if it occurs simultaneously with the cli instruction. the following example shows how this can be used to avoid interrupts during the timed eeprom write sequence.. when using the sei instruction to enable interr upts, the instruction following sei will be exe- cuted before any pending interrupts, as shown in this example. assembly code example in r16, sreg ; store sreg value cli ; disable interrupts during timed sequence sbi eecr, eempe ; start eeprom write sbi eecr, eepe out sreg, r16 ; restore sreg value (i-bit) c code example char csreg; csreg = sreg; /* store sreg value */ /* disable interrupts during timed sequence */ __disable_interrupt(); eecr |= (1< 16 8246b?avr?09/11 attiny2313a/4313 5. memories the avr architecture makes a distinction between program memory and data memory, locating each memory type in a separate address space. executable code is located in non-volatile pro- gram memory (flash), whereas data can be placed in either volatile (sram) or non-volatile memory (eeprom). see figure 5-1 , below. figure 5-1. memory overview. all memory spaces are linear and regular. 5.1 program memory (flash) attiny2313a/4313 contains 2/4k byte of on-chip , in-system reprogrammable flash memory for program storage. flash memories are non-volatile, i.e. they retain stored information even when not powered. since all avr instructions are 16 or 32 bits wi de, the flash is organized as 1024/2048 x 16 bits. the program counter (pc) is 10/11 bits wide, thus capable of addressing all 1024/2048 loca- tions of program memo ry, as illustrated in table 5-1 , below. constant tables can be allocated within the entire address space of program memory. see instructions lpm (load program memory), and spm (store program memory) in ?instruction set summary? on page 257 . flash program memory can also be programmed from an external device, as described in ?external programming? on page 184 . timing diagrams for instruction fetch and execution are presented in ?instruction execution tim- ing? on page 12 . the flash memory has a minimum endurance of 10,000 write/erase cycles. general purpo s e regi s ter file i/o regi s ter file extended i/o regi s ter file data memory data memory program memory fla s h s ram eeprom table 5-1. size of program memory (flash). device flash size address range attiny2313a 2kb 1024 words 0x0000 ? 0x03ff attiny4313 4kb 2048 words 0x0000 ? 0x07ff 17 8246b?avr?09/11 attiny2313a/4313 5.2 data memory (sram ) and register files table 5-2 shows how the data memory and register files of attiny2313a/4313 are organized. these memory areas are volatile, i.e. they do not retain information when power is removed. note: 1. also known as data address. this mode of addressing covers the entire data memory and reg- ister area. the address is contained in a 16-bit area of two-word instructions. 2. also known as direct i/o address. this mode of addressing covers part of the register area, only. it is used by instructions where the address is embedded in the instruction word. the 224/352 memory locations include the general purpose register file, i/o register file, extended i/o register file, and the internal data memory. for compatibility with future devices, reserved bits sh ould be written to zero, if accessed. reserved i/o memory addresses should never be written. 5.2.1 general purpose register file the first 32 locations are reserved for the gener al purpose register file. these registers are described in detail in ?general purpose register file? on page 11 . 5.2.2 i/o register file following the general purpose register file, the next 64 locations are reserved for i/o registers. registers in this area are used mainly for communicating with i/o and peripheral units of the device. data can be transferred between i/o space and the general purpose register file using instructions such as in, out, ld, st, and derivatives. all i/o registers in this area can be accessed wi th the instructions in and out. these i/o spe- cific instructions address the first location in the i/o register area as 0x00 and the last as 0x3f. the low 32 registers (address range 0x00...0x1f) are accessible by some bit-specific instruc- tions. in these registers, bits are easily set and cleared using sbi and cbi, while bit-conditional branches are readily constructed using instructions sbic, sbis, sbrc, and sbrs. registers in this area may also be ac cessed with instructi ons ld/ldd/ldi/lds and st/std/sts. these instructions treat the entire volatile memory as one data space and, there- fore, address i/o registers starting at 0x20. see ?instruction set summary? on page 257 . attiny2313a/4313 also contains three general purpo se i/o registers that can be used for storing any information. see gpior0, gpior1 and gpior2 in ?register summary? on page 255 . these general purpose i/o registers are particularly useful for storing global variables and status table 5-2. layout of data memory and register area. device memory area size long address (1) short address (2) attiny2313a general purpose register file 32b 0x000 ? 0x01f n/a i/o register file 64b 0x020 ? 0x05f 0x00 ? 0x3f data sram 128b 0x060 ? 0x0e0 n/a attiny4313 general purpose register file 32b 0x000 ? 0x01f n/a i/o register file 64b 0x020 ? 0x05f 0x00 ? 0x3f data sram 256b 0x060 ? 0x160 n/a 18 8246b?avr?09/11 attiny2313a/4313 flags, since they are accessible to bit-specific instructions such as sbi, cbi, sbic, sbis, sbrc, and sbrs. 5.2.3 data memory (sram) following the general purpose register file and the i/o register file, the remaining 128/256 loca- tions are reserved for the internal data sram. there are five addressing modes available: ? direct. this mode of addressing reaches the entire data space. ? indirect. ? indirect with displacement. this mode of addressing reaches 63 address locations from the base address given by the y- or z-register. ? indirect with pre-decrement. in this mode the address register is automatically decremented before access. address pointer registers (x, y, and z) are located in the general purpose register file, in registers r26 to r31. see ?general purpose register file? on page 11 . ? indirect with post-increment. in this mode the address register is automatically incremented after access. address pointer registers (x, y, and z) are located in the general purpose register file, in registers r26 to r31. see ?general purpose register file? on page 11 . all addressing modes can be used on the entire volatile memory, including the general purpose register file, the i/o register files and the data memory. internal sram is accessed in two clk cpu cycles, as illustrated in figure 5-2 , below. figure 5-2. on-chip data sram access cycles 5.3 data memory (eeprom) attiny2313a/4313 contains 128 bytes of non-vola tile data memory. this eeprom is organized as a separate data space, in which single byte s can be read and written. all access registers are located in the i/o space. clk wr rd data data address address valid t1 t2 t3 compute address read write cpu memory access instruction next instruction 19 8246b?avr?09/11 attiny2313a/4313 the eeprom memory lay out is summarised in table 5-3 , below. the internal 8mhz oscillator is used to time eeprom operations. the frequency of the oscillator must be within the requirements described in ?osccal ? oscillator calibration register? on page 32 . when powered by heavily filtered supplies, the supply voltage, v cc , is likely to rise or fall slowly on power-up and power-down. slow rise and fall times may put the device in a state where it is running at supply voltages lower than specified. to avoid problems in situations like this, see ?preventing eeprom corruption? on page 20 . the eeprom has a minimum endurance of 100,000 write/erase cycles. 5.3.1 programming methods there are two me thods for eeprom programming: ? atomic byte programming. this is the simple mode of programming, where target locations are erased and written in a single operation. in this mode of operation the target is guaranteed to always be erased before writing but programmin times are longer. ? split byte programming. it is possible to sp lit the erase and write cycle in two different operations. this is useful when short access times are required, for example when supply voltage is falling. in order to ta ke advantage of this method target locations must be erased before writing to them. this can be done at times when the system allows time-critical operations, typically at start-up and initialisation. the programming method is se lected using the eeprom progr amming mode bits (eepm1 and eepm0) in eeprom control register (eecr). see table 5-4 on page 24 . write and erase times are given in the same table. since programming takes some time the application must wait for one operation to complete before starting the next. this can be done by either polling the eeprom program enable bit (eepe) in eeprom control register (eecr), or via the eeprom ready interrupt. the eeprom interrupt is controlled by the eeprom ready interrupt enable (eerie) bit in eecr. 5.3.2 read to read an eeprom memo ry location follow the procedu re below: ? poll the eeprom program enable bit (eepe) in eeprom contro l register (eecr) to make sure no other eeprom operations are in process. if set, wait to clear. ? write target addre ss to eeprom address r egisters (eearh/eearl). ? start the read operation by setting the eep rom read enable bit (eere) in the eeprom control register (eecr). during the read operation, the cpu is halted for four clock cycles before executing the next instruction. ? read data from the eeprom data register (eedr). table 5-3. size of non-volatile data memory (eeprom). device eeprom size address range attiny2313a 128b 0x00 ? 0x7f attiny4313 256b 0x00 ? 0xff 20 8246b?avr?09/11 attiny2313a/4313 5.3.3 erase in order to prevent unintentional eeprom writes, a specific procedure must be followed to erase memory location s. to erase an eeprom memory loca tion follow the procedure below: ? poll the eeprom program enable bit (eepe) in eeprom contro l register (eecr) to make sure no other eeprom operations are in process. if set, wait to clear. ? set mode of programming to erase by wr iting eeprom programmin g mode bits (eepm0 and eepm1) in eeprom cont rol register (eecr). ? write target addre ss to eeprom address r egisters (eearh/eearl). ? enable erase by setting eeprom master pr ogram enable (eempe) in eeprom control register (eecr). within four clock cycles, st art the erase operation by setting the eeprom program enable bit (eepe) in the eeprom co ntrol register (eecr). during the erase operation, the cpu is halted for two clock cycles before executing the next instruction. the eepe bit remains set until the erase operation has completed. while the device is busy pro- gramming, it is not possible to perform an y other eeprom operations. 5.3.4 write in order to prevent unintentional eeprom writes, a specific procedure must be followed to write to memory locations. before writing data to eeprom the target location must be erased. this can be done either in the same operation or as part of a split operat ion. writing to an unerased eeprom location will result in corrupted data. to write an eeprom memory loca tion follow the procedure below: ? poll the eeprom program enable bit (eepe) in eeprom contro l register (eecr) to make sure no other eeprom operations are in process. if set, wait to clear. ? set mode of programming by writing eeprom programming mode bits (eepm0 and eepm1) in eeprom control regi ster (eecr). alternatively, data can be written in one operation or the write procedure can be split up in erase, only, and write, only. ? write target addre ss to eeprom address r egisters (eearh/eearl). ? write target data to eeprom data register (eedr). ? enable write by setting eeprom master pr ogram enable (eempe) in eeprom control register (eecr). within four clock cycles, start the write operation by setting the eeprom program enable bit (eepe) in the eeprom co ntrol register (eecr). during the write operation, the cpu is halted for two clock cycles before executing the next instruction. the eepe bit remains set until the write operatio n has completed. while the device is busy with programming, it is not possible to do any ot her eeprom operations. 5.3.5 preventing eeprom corruption during periods of low v cc , the eeprom data can be corrupted because the supp ly voltage is too low for the cpu and the eeprom to operate properly. these issues are the same as for board level systems using eepr om, and the same design so lutions should be applied. at low supply voltages data in eepr om can be corrupted in two ways: 21 8246b?avr?09/11 attiny2313a/4313 ? the supply voltage is too low to maintain proper operation of an otherwise legitimate eeprom program sequence. ? the supply voltage is too low for the cpu and instructions may be executed incorrectly. eeprom data corruption is avoide d by keeping the device in rese t during periods of insufficient power supply voltage. this is easily done by en abling the internal brown-out detector (bod). if bod detection levels are not sufficient for the design, an external reset circuit for low v cc can be used. provided that supply voltage is sufficient, an eeprom write operation will be completed even when a reset occurs. 5.3.6 program examples the following code examples show one assembly and one c function for erase, write, or atomic write of the eeprom. the examples assume that interrupts are controlled (e.g., by disabling interrupts globally) so that no interrupts occur during execution of these functions. note: see ?code examples? on page 7 . assembly code example eeprom_write: ; wait for completion of previous write sbic eecr, eepe rjmp eeprom_write ; set programming mode ldi r16, (0< 25 8246b?avr?09/11 attiny2313a/4313 ? bit 0 ? eere: eeprom read enable this is the read strobe of the eeprom. when the target addre ss has been set up in the eear, the eere bit must be written to one to trigger the eeprom read operation. eeprom read access takes one instruction, a nd the requested data is available immediately. when the eeprom is read , the cpu is halted fo r four cycles before th e next instruction is executed. the user should poll the eepe bit before starting the read operation. if a write operation is in progress, it not possible to read the eeprom, or to change the addre ss register (eear). 5.4.4 gpior2 ? general purpose i/o register 2 5.4.5 gpior1 ? general purpose i/o register 1 5.4.6 gpior0 ? general purpose i/o register 0 bit 76543210 0x15 (0x35) msb lsb gpior2 read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 0x14 (0x34) msb lsb gpior1 read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 0x13 (0x33) msb lsb gpior0 read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 26 8246b?avr?09/11 attiny2313a/4313 6. clock system figure 6-1 presents the principal clock systems in the avr and their distribution. all of the clocks need not be active at a given time. in order to reduce power consumption, the clocks to modules not being used can be halted by using different sleep modes, as described in ?power manage- ment and sleep modes? on page 34 . figure 6-1. clock distribution 6.1 clock subsystems 6.1.1 cpu clock ? clk cpu the cpu clock is routed to parts of the system concerned with operation of the avr core. examples of such modules are the general pur pose register file, the status register and the data memory holding the stack pointer. halting the cpu clock inhibits the core from performing general operations and calculations. 6.1.2 i/o clock ? clk i/o the i/o clock is used by the majority of the i/o modules, like timer/counters, and usart. the i/o clock is also used by the external interrupt module, but note that some external interrupts are detected by asynchronous logic, allowing such interrupts to be detected even if the i/o clock is halted. also note that start condition detection in the usi module is carried out asynchronously when clk i/o is halted, enabling usi start condition detection in all sleep modes. 6.1.3 flash clock ? clk flash the flash clock controls operation of the flash in terface. the flash clock is usually active simul- taneously with the cpu clock. general i/o modules cpu core ram clk i/o avr clock control unit clk cpu flash and eeprom clk flash source clock watchdog timer watchdog oscillator reset logic clock multiplexer watchdog clock calibrated rc oscillator crystal oscillator external clock 27 8246b?avr?09/11 attiny2313a/4313 6.2 clock sources the device has the following clock source options, selectable by flash fuse bits as shown below. the clock from the selected source is input to the avr clock generator, and routed to the appropriate modules. note: 1. for all fuses ?1? means unprogrammed while ?0? means programmed. the various choices for each clocking option is given in the following sections. when the cpu wakes up from power-down, the selected clock source is used to time the start-up, ensuring sta- ble oscillator operation before instruction execution starts. when the cpu starts from reset, there is an additional delay allowing the power to reach a stable level before commencing nor- mal operation. the watchdog oscillator is used for timing this real-time part of the start-up time. 6.2.1 default clock source the device is shipped with cksel = ?0100?, sut = ?10?, and ckdiv8 programmed. the default clock source setting is the internal rc oscillator with longes t start-up time and an initial system clock prescaling of 8, resulting in 1.0 mhz syst em clock. this default setting ensures that all users can make their desired clock source setting using an in-system or parallel programmer. for low-voltage devices it should be noted that unprogramming the ckdiv8 fuse may result in overclocking. at low voltages (below 2.7v) the devices are rated for maximum 4 mhz operation (see section 22.3 on page 200 ), but routing the clock signal from the internal oscillator directly to the system clock line will run the device at 8 mhz. 6.2.2 external clock to drive the device from an external clock source, xtal1 should be driven as shown in figure 6-2 . to run the device on an ex ternal clock, the cksel fuses must be programmed to ?0000?. table 6-1. device clocking select device clocking option cksel3..0 (1) external clock (see page 27 ) 0000 calibrated internal rc oscillator 4 mhz (see page 28 ) 0010 calibrated internal rc oscillator 8 mhz (see page 28 ) 0100 128 khz internal oscillator (see page 29 ) 0110 external crystal/ceramic resonator (see page 30 ) 1000 - 1111 reserved 0001/0011/0101/0111 28 8246b?avr?09/11 attiny2313a/4313 figure 6-2. external clock drive configuration when this clock source is sele cted, start-up times are determined by the sut fuses as shown in table 6-2 . when applying an external clock, it is required to avoid sudden changes in the applied clock fre- quency to ensure stable operation of the mcu. a variation in frequency of more than 2% from one clock cycle to the next can lead to unpredictable behavior. it is required to en sure that the mcu is kept in reset during such changes in the clock frequency. note that the system clock prescaler can be used to implement run-time changes of the internal clock frequency while still ensuring stable operation. see ?system clock prescaler? on page 31 for details. 6.2.3 calibrated internal rc oscillator the calibrated internal rc oscillator provides a fixed 8.0 mhz clock. the frequency is nominal value at 3v and 25 c. if 8 mhz frequency exceeds the speed specification of the device (depends on v cc ), the ckdiv8 fuse must be programmed in order to divide the internal fre- quency by 8 during start-up. the device is shipped with the ckdiv8 fuse programmed. this clock may be selected as the system clock by programming the cksel fuses as shown in table 6-3 . if selected, it will operate with no external comp onents. during rese t, hardware loads the calibration byte into the osccal register and thereby automatically calibrates the rc oscillator. at 3v and 25 c, this calibration gives a frequency within 10% of the nominal fre- quency. using calibration methods as described in application notes available at www.atmel.com/avr it is possible to achieve 2% accuracy at any given v cc and temperature. when this oscillator is used as the chip clock, the watchdog oscillator will still be used for the table 6-2. start-up times for the external clock selection sut1..0 start-up time from power- down and power-save additional delay from reset recommended usage 00 6 ck 14ck bod enabled 01 6 ck 14ck + 4 ms fast rising power 10 6 ck 14ck + 64 ms slowly rising power 11 reserved nc external clock signal xtal2 xtal1 gnd 29 8246b?avr?09/11 attiny2313a/4313 watchdog timer and for the reset time-out. for more information on the pre-programmed cali- bration value, see the section ?calibration byte? on page 181 . note: 1. the device is shipped with this option selected. when this oscillator is select ed, start-up times are determined by the sut fuses as shown in table 6-4 . notes: 1. if the rstdisbl fuse is pr ogrammed, this start-up time will be increased to 14ck + 4 ms to ensure programming mode can be entered. 2. the device is shipped with this option selected. 6.2.4 128 khz internal oscillator the 128 khz internal oscillator is a low power os cillator providing a clock of 128 khz. the fre- quency is nominal at 3 v and 25 c. this clock may be selected as the system clock by programming the cksel fuses to 0110. when this clock source is sele cted, start-up times are determined by the sut fuses as shown in table 6-5 . note: 1. if the rstdisbl fuse is pr ogrammed, this start-up time will be increased to 14ck + 4 ms to ensure programming mode can be entered. table 6-3. internal calibrated rc o scillator operating modes cksel3..0 nominal frequency 0010 4.0 mhz 0100 8.0 mhz (1) table 6-4. start-up times for the internal calib rated rc oscillato r clock selection sut1..0 start-up time from power- down and power-save additional delay from reset recommended usage 00 6 ck 14ck (1) bod enabled 01 6 ck 14ck + 4 ms fast rising power 10 (2) 6 ck 14ck + 64 ms slowly rising power 11 reserved table 6-5. start-up times for the 128 khz internal oscillator sut1..0 start-up time from power- down and power-save additional delay from reset recommended usage 00 6 ck 14ck (1) bod enabled 01 6 ck 14ck + 4 ms fast rising power 10 6 ck 14ck + 64 ms slowly rising power 11 reserved 30 8246b?avr?09/11 attiny2313a/4313 6.2.5 crystal oscillator xtal1 and xtal2 are input and output, respectively, of an inverting amplifier which can be con- figured for use as an on-chip oscillator, as shown in figure 6-3 on page 30 . either a quartz crystal or a ceramic resonator may be used. c1 and c2 should always be equal for both crystals and resonators. the optimal value of the capacitors depends on the crystal or resonator in use, the amount of stray capacitance, and the electromagnetic noise of the environment. some initial guidelines for choosing capacitors for use with crystals are given in table 6-6 on page 30 . for ceramic resonators, the capacitor val- ues given by the manufacturer should be used. figure 6-3. crystal oscillator connections the oscillator can operate in three different mo des, each optimized for a specific frequency range. the op erating mode is selected by t he fuses cksel3..1 as shown in table 6-6 . note: 1. this option should not be used with crystals, only with ceramic resonators. the cksel0 fuse together with the sut1..0 fuses select the start-up times as shown in table 6-7 . table 6-6. crystal oscillator operating modes cksel3..1 frequency range (mhz) recommended range for capacitors c1 and c2 for use with crystals (pf) 100 (1) 0.4 - 0.9 ? 101 0.9 - 3.0 12 - 22 110 3.0 - 8.0 12 - 22 111 8.0 - 12 - 22 xtal2 xtal1 gnd c2 c1 31 8246b?avr?09/11 attiny2313a/4313 notes: 1. these options should only be used when not operating close to the maximum frequency of the device, and only if frequency stability at start- up is not important for the application. these options are not suitable for crystals. 2. these options are intended for use with cerami c resonators and will ensure frequency stability at start-up. they can also be used with crystal s when not operating close to the maximum fre- quency of the device, and if frequency stability at start-up is not important for the application. 6.3 system clock prescaler the attiny2313a/4313 has a system clock pres caler, and the system clock can be divided by setting the ?clkpr ? clock prescale register? on page 32 . this feature can be used to decrease the system clock frequency and the power consumption when the requirement for pro- cessing power is low. this can be used with all cl ock source options, and it will affect the clock frequency of the cpu and all synchronous peripherals. clk i/o , clk cpu , and clk flash are divided by a factor as shown in table 6-8 on page 33 . 6.3.1 switching time when switching between prescaler settings, the system clock prescaler ensures that no glitches occurs in the clock system. it also ensures that no intermediate frequency is higher than neither the clock frequency corresponding to the previous setting, nor the clock frequency corre- sponding to the new setting. the ripple counter that implements the prescaler runs at the frequency of the undivided clock, which may be faster than the cpu's clock frequency. hence, it is not possible to determine the state of the prescaler - even if it were readable, and the exact time it takes to switch from one clock division to the other cann ot be exactly predicted. from th e time the clkps values are writ- ten, it takes between t1 + t2 and t1 + 2 * t2 before the new clock frequency is active. in this interval, two active clock edges are produced. here, t1 is the previous clock period, and t2 is the period corresponding to the new prescaler setting. table 6-7. start-up times for the crysta l oscillator clock selection cksel0 sut1..0 start-up time from power-down and power-save additional delay from reset (v cc = 5.0v) recommended usage 0 00 258 ck (1) 14ck + 4 ms ceramic resonator, fast rising power 0 01 258 ck (1) 14ck + 64 ms ceramic resonator, slowly rising power 010 1k ck (2) 14ck ceramic resonator, bod enabled 011 1k ck (2) 14ck + 4 ms ceramic resonator, fast rising power 100 1k ck (2) 14ck + 64 ms ceramic resonator, slowly rising power 1 01 16k ck 14ck crystal oscillator, bod enabled 1 10 16k ck 14ck + 4 ms crystal oscillator, fast rising power 1 11 16k ck 14ck + 64 ms crystal oscillator, slowly rising power 32 8246b?avr?09/11 attiny2313a/4313 6.4 clock output buffer the device can output the system clock on the ckout pin. to enable this, the ckout fuse has to be programmed. this mode of operation is useful when the chip clock is needed to drive other circuits in the system. note that the clock will not be out put during reset and that the no rmal operation of the i/o pin will be overridden when the fuse is programmed. any clock source, including the internal rc oscil- lator, can be selected when the clock is output on ckout pin. if the system clock prescaler is used, it is the divided system clock that is output. 6.5 register description 6.5.1 osccal ? oscillato r calibration register ? bit 7 ? res: reserved bit this bit is reserved bit in attiny 2313a/4313 and it will always read zero. ? bits 6:0 ? cal[6:0]: oscillator calibration value writing the calibration byte to this address will trim the internal oscillator to remove process vari- ations from the oscillator frequency. this is done automatically during chip reset. when osccal is zero, the lowest available frequency is chosen. writing non-zero values to this regis- ter will increase the frequency of the internal oscillator. writing 0x7f to the register gives the highest available frequency. the calibrated oscillator is used to time eeprom and flash access. if eeprom or flash is written, do not calibrate to more than 10% above the nominal frequency. otherwise, the eeprom or flash write may fail. no te that the oscillator is intended for calibra tion to 8 mhz or 4 mhz. tuning to other values is not guaranteed, as indicated in table 6-8 below. to ensure stable operation of the mcu the calibration value should be changed in small steps. a variation in frequency of more than 2% from one cycle to the next can lead to unpredicatble behavior. changes in osccal should not exceed 0x20 for each calibration. it is required to ensure that the mcu is kept in reset during such changes in the clock frequency. 6.5.2 clkpr ? clock prescale register ? bit 7 ? clkpce: clock prescaler change enable the clkpce bit must be written to logic one to enab le change of the clkps bits. the clkpce bit is only updated when the other bits in cl kpr are simultaneously wr itten to zero. clkpce is cleared by hardware four cycles af ter it is written or when the clkps bits are written. rewriting bit 76543210 0x31 (0x51) ? cal6 cal5 cal4 cal3 cal2 cal1 cal0 osccal read/write r r/w r/w r/w r/w r/w r/w r/w initial value 0 device specific calibration value bit 7 6 5 4 3 2 1 0 0x26 (0x46) clkpce ? ? ? clkps3 clkps2 clkps1 clkps0 clkpr read/write r/w r r r r/w r/w r/w r/w initial value 0 0 0 0 see bit description 33 8246b?avr?09/11 attiny2313a/4313 the clkpce bit within this time-out period does neither extend the time-out period, nor clear the clkpce bit. ? bits 6:4 ? res: reserved bits these bits are reserved bits in the atti ny2313a/4313 and will always read as zero. ? bits 3:0 ? clkps3:0: clock prescaler select bits 3 - 0 these bits define the division factor between the selected clock source and the internal system clock. these bits can be written run-time to vary the clock frequency to suit the application requirements. as the divider divides the master clock input to the mcu, the speed of all synchro- nous peripherals is reduced when a division fact or is used. the division factors are given in table 6-8 on page 33 . to avoid unintentional changes of clock frequency, a special write procedure must be followed to change the clkps bits: 1. write the clock prescaler change enable (clkpce) bit to one and all other bits in clkpr to zero. 2. within four cycles, write the desired valu e to clkps while writing a zero to clkpce. interrupts must be disabled when changing prescaler setting to make sure the write procedure is not interrupted. the application software must ensure that a sufficient division factor is chosen if the selected clock source has a higher frequency than the maximum frequency of the device at the present operating conditions. the device is shipped with the ckdiv8 fuse programmed. table 6-8. clock prescaler select clkps3 clkps2 clkps1 clkps0 clock division factor 0000 1 0001 2 0010 4 0011 8 0100 16 0101 32 0110 64 0111 128 1000 256 1001 reserved 1010 reserved 1011 reserved 1100 reserved 1101 reserved 1110 reserved 1111 reserved 34 8246b?avr?09/11 attiny2313a/4313 7. power management and sleep modes the high performance and industry leading code efficiency makes the avr microcontrollers an ideal choise for low power applications. in addition, sleep modes enable the application to shut down unused modules in the mcu, thereby saving power. the avr provides various sleep modes allowing the user to tailor the power consumption to the application?s requirements. 7.1 sleep modes figure 6-1 on page 26 presents the different clock systems and their distribution in attiny2313a/4313. the figure is helpful in selecting an appropriate sleep mode. table 7-1 shows the different sleep modes and their wake up sources. note: 1. for int0 and int1, only level interrupt. to enter any of the three sleep modes, the se bit in mcucr must be written to logic one and a sleep instruction must be executed. the sm1..0 bits in the mcucr register select which sleep mode (idle, standby or power-down) will be activated by the sl eep instruction. see table 7-2 on page 37 for a summary. if an enabled interrupt occurs while the mcu is in a sleep mode, the mcu wakes up. the mcu is then halted for four cycles in addition to the st art-up time, executes the interrupt routine, and resumes execution from the instruction followi ng sleep. the contents of the register file and sram are unaltered when the device wakes up from sleep. if a reset occurs during sleep mode, the mcu wakes up and executes from the reset vector. note that if a level triggered interrupt is used for wake-up the changed level must be held for some time to wake up the mcu (and for the mcu to enter the interrupt service routine). see ?external interrupts? on page 49 for details. 7.1.1 idle mode when the sm1..0 bits are wri tten to 00, the sleep instruction makes the mcu enter idle mode, stopping the cpu but allowing analog comparator, usi, timer/counter, watchdog, and the interrupt system to continue operating. this sleep mode basically halts clk cpu and clk flash , while allowing the other clocks to run. idle mode enables the mcu to wake up from external triggered interrupts as well as internal ones like the timer overflow. if wake-up from the analog comparator interrupt is not required, the analog comparator can be powered down by setting the acd bit in ?acsr ? analog com- table 7-1. active clock domains and wake-up sources in different sleep modes sleep mode active clock domains oscillators wake-up sources clk cpu clk flash clk io main clock source enabled int0, int1 and pin change usi start condition spm/eeprom ready interrupt other i/o watchdog interrupt idle x x xxxxx power-down x (1) xx stand-by x x (1) xx 35 8246b?avr?09/11 attiny2313a/4313 parator control and status register? on page 168 . this will reduce power consumption in idle mode. 7.1.2 power-down mode when the sm1:0 bits are written to 01/11, the sleep instruction makes the mcu enter power- down mode. in this mode, the os cillator is stopped, while the ex ternal interrupts, and the watch- dog continue operating (if enabled). only an external reset, a watchdog reset, a brown-out reset, an external level interrupt on int0 and int1, or a pin change interrupt can wake up the mcu. this sleep mode halts all generated clocks, allowing operation of asynchronous modules only. 7.1.3 standby mode when the sm1..0 bits are 10 and an external crystal/resonator clock option is selected, the sleep instruction makes the mcu enter standby mode. this mode is identical to power-down with the exception that the oscillator is kept running. fr om standby mode, the device wakes up in six clock cycles. 7.2 software bod disable when the brown-out detector (bod) is enabled by bodlevel fuses (see table 20-4 on page 179 ), the bod is actively monitoring the supply vo ltage during a sleep period. in some devices it is possible to save power by disabling the bod by software in power-down and stand-by sleep modes. the sleep mode power consum ption will then be at the same level as when bod is glob- ally disabled by fuses. if bod is disabled by software, the bod function is turned off immediately after entering the sleep mode. upon wake-up from sleep, bod is automatically enabled again. this ensures safe operation in case the v cc level has dropped during the sleep period. when the bod has been disabled, the wake-up time from sleep mode will be approximately 60s to ensure that the bod is working corr ectly before the mcu continues executing code. bod disable is controlled by the bods (bod sleep) bit of bod control register, see ?bodcr ? brown-out detector control register? on page 38 . writing this bit to one turns off bod in power-down and stand-by, while writing a zero keeps the bod active. the default setting is zero, i.e. bod active. writing to the bods bit is controlled by a timed sequence and an enable bit, see ?bodcr ? brown-out detector control register? on page 38 . 7.3 power reduction register the power reduction register (prr), see ?prr ? power reduction register? on page 37 , pro- vides a method to reduce power consumption by stopping the clock to individual peripherals. when the clock for a peripheral is stopped then: ? the current state of the peripheral is frozen. ? the associated registers can not be read or written. ? resources used by the perip heral will remain occupied. the peripheral should in most cases be disabled before stopping the clock. clearing the prr bit wakes up the peripheral and puts it in the same state as before shutdown. 36 8246b?avr?09/11 attiny2313a/4313 peripheral shutdown can be used in idle mode an d active mode to significantly reduce the over- all power consumption. see ?effect of power reduction? on page 206 for examples. in all other sleep modes, the clock is already stopped. 7.4 minimizing power consumption there are several issues to consider when trying to minimize the power consumption in an avr controlled system. in general, sleep modes should be used as much as possible, and the sleep mode should be selected so that as few as possi ble of the device?s functions are operating. all functions not needed should be disabled. in particular, the following modules may need special consideration when trying to achieve th e lowest possible power consumption. 7.4.1 analog comparator when entering idle mode, the analog comparator should be disabled if not used. in the other sleep modes, the analog comparator is automatically disabled. however, if the analog compar- ator is set up to use the internal voltage reference as input, the analog comparator should be disabled in all sleep modes. otherwise, the internal voltage reference will be enabled, indepen- dent of sleep mode. see ?analog comparator? on page 168 for details on how to configure the analog comparator. 7.4.2 internal voltage reference the internal voltage re ference will be enabled when needed by the brown-out detection or the analog comparator. if these modules are disabled as described in the sections above, the inter- nal voltage reference will be disabled and it will not be consuming power. when turned on again, the user must allow the reference to start up before the output is used. if the reference is kept on in sleep mode, the output can be used immediately. see ?internal voltage reference? on page 42 for details on the start-up time. 7.4.3 brown-out detector if the brown-out detector is not needed in the application, this module should be turned off. if the brown-out detector is enabled by the bodlevel fuses, it will be enabled in all sleep modes, and hence, always consume power. in the deeper sleep modes, this will contribute significantly to the total current consumption. see ?brown-out detection? on page 41 and ?software bod dis- able? on page 35 for details on how to configure the brown-out detector. 7.4.4 watchdog timer if the watchdog timer is not needed in the application, this module should be turned off. if the watchdog timer is enabled, it will be enabled in all sleep modes, and hence, always consume power. in the deeper slee p modes, this will contribute signific antly to the total current consump- tion. see ?interrupts? on page 48 for details on how to configure the watchdog timer. 7.4.5 port pins when entering a sleep mode, all port pins should be configured to use minimum power. the most important thing is then to ensure that no pins drive resistive loads. in sleep modes where the i/o clock (clk i/o ) is stopped, the input bu ffers of the device will be disabled. this ensures that no power is consumed by the input logic when not needed. in some cases, the input logic is needed for detecting wake-up conditions, and it will then be enabled. see the section ?digital input enable and sleep modes? on page 58 for details on which pins are enabled. if the input buffer is enabled and the input signal is left fl oating or has an analog signal level close to v cc /2, the input buffer will use excessive power. 37 8246b?avr?09/11 attiny2313a/4313 for analog input pins, the digital input buffer should be disabled at all times. an analog signal level close to v cc /2 on an input pin can cause significant current even in active mode. digital input buffers can be disabled by writing to the digital input disable register (didr). see ?didr ? digital input disable register? on page 169 for details. 7.5 register description 7.5.1 mcucr ? mcu control register the sleep mode control register contains control bits for power management. ? bits 6, 4 ? sm1..0: sleep mode select bits 1 and 0 these bits select between the four available sleep modes as shown in table 7-2 . note: standby mode is only recommended for use with external crystals or resonators. ? bit 5 ? se: sleep enable the se bit must be written to logic one to make the mcu enter the sleep mode when the sleep instruction is executed. to avoid the mcu enteri ng the sleep mode unless it is the programmer?s purpose, it is recommended to write the sleep enable (se) bit to one just before the execution of the sleep instruction and to clear it immediately af ter waking up. 7.5.2 prr ? power reduction register the power reduction register provides a met hod to reduce power consumption by allowing peripheral clock signals to be disabled. ? bits 7..4 ? res: reserved bits these bits are reserved and will always read zero. ? bit 3 ? prtim1: power reduction timer/counter1 writing a logic one to this bit shuts down the timer/counter1 module. when the timer/counter1 is enabled, operation will cont inue like before the shutdown. bit 76543210 0x35 (0x55) pud sm1 se sm0 isc11 isc10 isc01 isc00 mcucr read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 table 7-2. sleep mode select sm1 sm0 sleep mode 00idle 0 1 power-down 1 0 standby 1 1 power-down bit 7654 3 2 1 0 0x06 (0x26) ? ? ? ? prtim1 prtim0 prusi prusart prr read/write r r r r r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 38 8246b?avr?09/11 attiny2313a/4313 ? bit 2 ? prtim0: power reduction timer/counter0 writing a logic one to this bit shuts down the timer/counter0 module. when the timer/counter0 is enabled, operation will cont inue like before the shutdown. ? bit 1 ? prusi: power reduction usi writing a logic one to this bit shuts down t he usi by stopping the clock to the module. when waking up the usi again, the usi should be re initialized to ensure proper operation. ? bit 0 ? prusart: power reduction usart writing a logic one to this bit shuts down t he usi by stopping the clock to the module. when waking up the usi again, the usi should be re initialized to ensure proper operation. 7.5.3 bodcr ? brown-out detector control register the bod control register contains control bits for disabling the bod by software. ? bit 1 ? bods: bod sleep in order to disable bod during sleep the bods bit must be written to logic one. this is controlled by a timed sequence and the enable bit, bodse. first, both bods and bodse must be set to one. second, within four clock cycles, bods must be set to one and bodse must be set to zero. the bods bit is active thre e clock cycles after it is set. a sleep instruction must be exe- cuted while bods is active in order to turn off the bod for the actual sleep mode. the bods bit is automatically cleared after three clock cycles. ? bit 0 ? bodse: bod sleep enable the bodse bit enables setting of bods control bit, as explained on bods bit description. bod disable is controlled by a timed sequence. bit 76543210 0x07 (0x27) ??????bodsbodsebodcr read/writerrrrrrr/wr/w initial value 0 0 0 0 0 0 0 0 39 8246b?avr?09/11 attiny2313a/4313 8. system control and reset 8.1 resetting the avr during reset, all i/o registers are set to their initial values, and the program starts execution from the reset vector. the instruction placed at the reset vector must be a rjmp ? relative jump ? instruction to the reset handling routine. if the program never enables an interrupt source, the interrupt vectors are not used, and regular program code can be placed at these locations. the circuit diagram in figure 8-1 shows the reset logic. electrical parameters of the reset circuitry are given in table 22-3 on page 201 . figure 8-1. reset logic the i/o ports of the avr are immediately reset to their initial state when a reset source goes active. this does not require any clock source to be running. after all reset sources have gone inactive, a delay counter is invoked, stretching the internal reset. this allows the power to reach a stable level before normal operation starts. the time-out period of the delay counter is defined by the user through the sut and cksel fuses. the dif- ferent selections for the delay period are presented in ?clock sources? on page 27 . mcu status register (mcusr) brown-out reset circuit bodlevel [2..0] delay counters cksel[3:0] ck timeout wdrf borf extrf porf data b u s clock generator spike filter pull-up resistor watchdog oscillator sut[1:0] power-on reset circuit rstdisbl 40 8246b?avr?09/11 attiny2313a/4313 8.2 reset sources the attiny2313a/4313 has four sources of reset: ? power-on reset. the mcu is reset when the supply voltage is below the power-on reset threshold (v pot ) ? external reset. the mcu is reset when a low level is present on the reset pin for longer than the minimum pulse length when reset function is enabled ? watchdog reset. the mcu is reset when the watchdog timer period expires and the watchdog is enabled ? brown-out reset. the mcu is re set when the supply voltage v cc is below the brown-out reset threshold (v bot ) and the brown-out detector is enabled 8.2.1 power-on reset a power-on reset (por) pulse is generated by an on-chip detection circuit. the detection level is defined in ?system and reset characteristics? on page 201 . the por is activated whenever v cc is below the detection level. the por circuit can be used to trigger the start-up reset, as well as to detect a fa ilure in supply voltage. a power-on reset (por) circuit ensures that the device is reset from power-on. reaching the power-on reset threshold voltage invokes the delay counter, which determines how long the device is kept in reset after v cc rise. the reset signal is activated again, without any delay, when v cc decreases below the detection level. figure 8-2. mcu start-up, reset tied to v cc figure 8-3. mcu start-up, reset extended externally v reset time-out internal reset t tout v pot v rst cc reset time-out internal reset t tout v pot v rst v cc 41 8246b?avr?09/11 attiny2313a/4313 8.2.2 external reset an external reset is generated by a low level on the reset pin if enabled. reset pulses longer than the minimum pulse width (see ?system and reset characteristics? on page 201 ) will gener- ate a reset, even if the clock is not running. shorter pulses are not guaranteed to generate a reset. when the applied signal reaches the reset threshold voltage ? v rst ? on its positive edge, the delay counter starts the mcu after the time-out period ? t tout ? has expired. figure 8-4. external reset during operation 8.2.3 brown-out detection attiny2313a/4313 has an on-chip brown-out de tection (bod) circuit for monitoring the v cc level during operation by comparing it to a fixed trigger level. the trigger level for the bod can be selected by the bodlevel fu ses. the trigger level has a h ysteresis to ensure spike free brown-out detection. the hysteresis on the detection level should be interpreted as v bot+ = v bot + v hyst /2 and v bot- = v bot - v hyst /2. when the bod is enabled, and v cc decreases to a value below the trigger level (v bot- in figure 8-5 on page 41 ), the brown-out reset is immediately activated. when v cc increases above the trigger level (v bot+ in figure 8-5 on page 41 ), the delay counter starts the mcu after the time- out period t tout has expired. the bod circuit will only detect a drop in v cc if the voltage stays below the trigger level for lon- ger than t bod given in ?system and reset characteristics? on page 201 . figure 8-5. brown-out reset during operation cc v cc reset time-out internal reset v bot- v bot+ t tout 42 8246b?avr?09/11 attiny2313a/4313 8.2.4 watchdog reset when the watchdog times out, it will generate a short reset pulse of one ck cycle duration. on the falling edge of this pulse, the delay timer starts counting the time-out period t tout . see ?interrupts? on page 48 for details on operation of the watchdog timer. figure 8-6. watchdog reset during operation 8.3 internal voltage reference attiny2313a/4313 features an internal bandgap reference. this reference is used for brown-out detection, and it can be used as an input to the analog comparator. the bandgap voltage varies with supply voltage and temperature. 8.3.1 voltage reference enable signals and start-up time the voltage reference has a start-up time that may influence the way it should be used. the start-up time is given in ?system and reset characteristics? on page 201 . to save power, the reference is not always turned on. the reference is on during the following situations: 1. when the bod is enabled (by prog ramming the bodlevel [2..0] fuse). 2. when the internal reference is connected to the analog comparator (by setting the acbg bit in acsr). thus, when the bod is not enabled, after setting the acbg bit, the user must always allow the reference to start up before the output from the analog comparator. to reduce power consump- tion in power-down mode, the user can avoid the three conditions above to ensure that the reference is turned off before entering power-down mode. 8.4 watchdog timer the watchdog timer is clocked fr om an on-chip oscillator which runs at 128 khz. by controlling the watchdog timer prescaler, the watchdog reset interval can be adjusted as shown in table 8-3 on page 47 . the wdr ? watchdog reset ? instruction resets the watchdog timer. the watchdog timer is also reset when it is disabled and when a chip reset occurs. ten different clock cycle periods can be selected to determine the reset period. if the reset period expires without another watchdog reset, the attiny2313a/4313 resets and executes from the reset vector. for timing details on the watchdog reset, refer to table 8-3 on page 47 . ck cc 43 8246b?avr?09/11 attiny2313a/4313 the watchdog timer can also be configured to generate an interrupt instead of a reset. this can be very helpful when using the watchdog to wake-up from power-down. to prevent unintentional disabling of the watchdog or unintentional change of time-out period, two different safety levels are selected by the fuse wdton as shown in table 8-1 see ?timed sequences for changing the configuration of the watchdog timer? on page 43 for details. figure 8-7. watchdog timer 8.4.1 timed sequences for changing the configuration of the watchdog timer the sequence for changing configuration differs slightly between the two safety levels. separate procedures are described for each level. ? safety level 1 in this mode, the watchdog ti mer is initially disabled, but can be enabled by writing the wde bit to one without any restriction. a timed sequence is needed when disabling an enabled watchdog timer. to disable an enabl ed watchdog timer, the following procedure must be followed: a. in the same operation, write a logic one to wdce and wde. a logic one must be written to wde regardless of the previous value of the wde bit b. within the next four clock cycles, in the same operation, write the wde and wdp bits as desired, but with the wdce bit cleared table 8-1. wdt configuration as a function of the fuse settings of wdton wdton safety level wdt initial state how to disable the wdt how to change time- out unprogrammed 1 disabled timed sequence no limitations programmed 2 enabled always enabled timed sequence osc/2k osc/4k osc/8k osc/16k osc/32k osc/64k osc/128k osc/256k osc/512k osc/1024k mcu reset watchdog prescaler 128 khz oscillator watchdog reset wdp0 wdp1 wdp2 wdp3 wde mux 44 8246b?avr?09/11 attiny2313a/4313 ? safety level 2 in this mode, the watchdog timer is always enabled, an d the wde bit will always read as one. a timed sequence is needed when changing the watchdog time-out period. to change the watchdog time-out, the following procedure must be followed: a. in the same operation, write a logical one to wdce and wde. even though the wde always is set, the wde must be written to one to start the timed sequence b. within the next four clock cycles, in the same operation, write the wdp bits as desired, but with the wdce bit cleared. the value written to the wde bit is irrelevant 8.4.2 code example the following code example shows one assembly and one c function for turning off the wdt. the example assumes that interrupts are controlled (e.g., by disabling interrupts globally) so that no interrupts will occur during execution of these functions. note: 1. see ?code examples? on page 7. assembly code example (1) wdt_off: wdr ; clear wdrf in mcusr ldi r16, (0< 46 8246b?avr?09/11 attiny2313a/4313 the next time-out will generate a reset. to avoid the watchdog reset, wdie must be set after each interrupt. ? bit 4 ? wdce: watchdog change enable this bit must be set when the wde bit is writte n to logic zero. otherwis e, the watchdog will not be disabled. once written to one, hardware will clear this bit after four clock cycles. see the description of the wde bit for a watchdog disable procedure. this bit must also be set when changing the prescaler bits. see ?timed sequences for changing the configuration of the watchdog timer? on page 43 . ? bit 3 ? wde: watchdog enable when the wde is written to logic one, the watchdog timer is enabled, and if the wde is written to logic zero, the watchdog timer function is di sabled. wde can only be cleared if the wdce bit has logic level one. to disable an enabled watchdog timer, the following procedure must be followed: 1. in the same operation, write a logic one to wdce and wde. a logic one must be writ- ten to wde even though it is set to one before the disable operation starts. 2. within the next four clock cycles, write a logic 0 to wde. this disables the watchdog. in safety level 2, it is not possible to disable the watchdog timer, even with the algorithm described above. see ?timed sequences for changing the configuration of the watchdog timer? on page 43 . in safety level 1, wde is overridden by wdrf in mcusr. see ?mcusr ? mcu status regis- ter? on page 45 for description of wdrf. this means that wde is always set when wdrf is set. to clear wde, wdrf must be cleared before disabling the watchdog with the procedure described above. this feature ensures multiple re sets during conditions causing failure, and a safe start-up after the failure. note: if the watchdog timer is not going to be used in the application, it is important to go through a watchdog disable procedure in the initialization of the device. if the watchdog is accidentally enabled, for example by a runaway pointer or brown-out condition, the device will be reset, which in turn will lead to a new watchdog reset. to avoi d this situation, the app lication software should always clear the wdrf flag and the wde control bit in the initialization routine. table 8-2. watchdog timer configuration wde wdie watchdog timer state action on time-out 0 0 stopped none 0 1 running interrupt 1 0 running reset 1 1 running interrupt 47 8246b?avr?09/11 attiny2313a/4313 ? bits 5, 2..0 ? wdp3..0: watchdog timer prescaler 3, 2, 1, and 0 the wdp3..0 bits determine the watchdog timer prescaling when the watchdog timer is enabled. the different prescaling values and their corresponding timeout periods are shown in table 8-3 on page 47 . note: 1. if selected, one of the valid settings below 0b1010 will be used. table 8-3. watchdog timer prescale select wdp3 wdp2 wdp1 wdp0 number of wdt oscillator cycles typical time-out at v cc = 5.0v 0 0 0 0 2k cycles 16 ms 0 0 0 1 4k cycles 32 ms 0 0 1 0 8k cycles 64 ms 0 0 1 1 16k cycles 0.125 s 0 1 0 0 32k cycles 0.25 s 0 1 0 1 64k cycles 0.5 s 0 1 1 0 128k cycles 1.0 s 0 1 1 1 256k cycles 2.0 s 1 0 0 0 512k cycles 4.0 s 1 0 0 1 1024k cycles 8.0 s 1010 reserved (1) 1011 1100 1101 1110 1111 48 8246b?avr?09/11 attiny2313a/4313 9. interrupts this section describes the specifics of the interrupt handling as performed in attiny2313a/4313. for a general explanation of the avr interrupt handling, refer to ?reset and interrupt handling? on page 13 . 9.1 interrupt vectors the interrupt vectors of attiny2313a/4313 are described in table 9-1 below in case the program never enab les an interrupt source, the interrupt vectors will not be used and, consequently, regular program code can be placed at these locations. table 9-1. reset and interrupt vectors vector no. program address label interrupt source 1 0x0000 reset external pin, power-on reset, brown-out reset, and watchdog reset 2 0x0001 int0 external interrupt request 0 3 0x0002 int1 external interrupt request 1 4 0x0003 timer1 capt timer/counter1 capture event 5 0x0004 timer1 compa timer/counter1 compare match a 6 0x0005 timer1 ovf timer/counter1 overflow 7 0x0006 timer0 ovf timer/counter0 overflow 8 0x0007 usart0, rx usart0, rx complete 9 0x0008 usart0, udre usart0 data register empty 10 0x0009 usart0, tx usart0, tx complete 11 0x000a analog comp analog comparator 12 0x000b pcint0 pin change interrupt request 0 13 0x000c timer1 compb timer/c ounter1 compare match b 14 0x000d timer0 compa timer/c ounter0 compare match a 15 0x000e timer0 compb timer/counter0 compare match b 16 0x000f usi start usi start condition 17 0x0010 usi overflow usi overflow 18 0x0011 ee ready eeprom ready 19 0x0012 wdt overflow watchdog timer overflow 20 0x0013 pcint1 pin change interrupt request 1 21 0x0014 pcint2 pin change interrupt request 2 49 8246b?avr?09/11 attiny2313a/4313 the most typical and general setup for the interrupt vector addresses in attiny2313a/4313 shown below: address labels code comments 0x0000 rjmp reset ; reset handler 0x0001 rjmp int0 ; external interrupt0 handler 0x0002 rjmp int1 ; external interrupt1 handler 0x0003 rjmp tim1_capt ; timer1 capture handler 0x0004 rjmp tim1_compa ; timer1 comparea handler 0x0005 rjmp tim1_ovf ; timer1 overflow handler 0x0006 rjmp tim0_ovf ; timer0 overflow handler 0x0007 rjmp usart0_rxc ; usart0 rx complete handler 0x0008 rjmp usart0_dre ; usart0,udr empty handler 0x0009 rjmp usart0_txc ; usart0 tx complete handler 0x000a rjmp ana_comp ; analog comparator handler 0x000b rjmp pcint0 ; pcint0 handler 0x000c rjmp timer1_compb ; timer1 compare b handler 0x000d rjmp timer0_compa ; timer0 compare a handler 0x000e rjmp timer0_compb ; timer0 compare b handler 0x000f rjmp usi_start ; usi start handler 0x0010 rjmp usi_overflow ; usi overflow handler 0x0011 rjmp ee_ready ; eeprom ready handler 0x0012 rjmp wdt_overflow ; watchdog overflow handler 0x0013 rjmp pcint1 ; pcint1 handler 0x0014 rjmp pcint2 ; pcint2 handler ; 0x0013 reset: ldi r16, low(ramend); main program start 0x0014 out spl,r16 set stack pointer to top of ram 0x0015 sei ; enable interrupts 0x0016 50 8246b?avr?09/11 attiny2313a/4313 9.2.1 low level interrupt a low level interrupt on int0 or int1 is detected asynchronously. this means that the interrupt source can be used for waking the part also from sleep modes other than idle (the i/o clock is halted in all sleep modes except idle). note that if a level triggered interrupt is used for wake-up from power-down, the required level must be held long enough for the mcu to complete the wake-up to trigger the level interrupt. if the level disappears before the end of the start-up ti me, the mcu will still wake up, but no inter- rupt will be generated. the start-up time is defined by the sut and cksel fuses, as described in ?clock system? on page 26 . if the low level on the interrupt pin is removed before the device has woken up then program execution will not be diverted to the interrupt service ro utine but continue from the instruction fol- lowing the sleep command. 9.2.2 pin change interrupt timing a timing example of a pin change interrupt is shown in figure 9-1 . figure 9-1. timing of pin change interrupts clk pcint(0) pin_lat pin_sync pcint_in_(0) pcint_syn pcint_setflag pcif pcint(0) pin_sync pcint_syn pin_lat d q le pcint_setflag pcif clk clk pcint(0) in pcmsk(x) pcint_in_(0) 0 x 51 8246b?avr?09/11 attiny2313a/4313 9.3 register description 9.3.1 mcucr ? mcu control register the external interrupt control register contains control bits for interrupt sense control. ? bit 3, 2 ? isc11, isc10: interrupt sense control 1 bit 1 and bit 0 the external interrupt 1 is activated by the exte rnal pin int1 if the sreg i-flag and the corre- sponding interrupt mask are set. the level and edges on the external int1 pin that activate the interrupt are defined in table 9-2 . the value on the int1 pin is sampled before detecting edges. if edge or toggle interrupt is selected, pulses that last longer than one clock period will generate an interrupt. shorter pulses are not guaranteed to generate an interrupt. if low level interrupt is selected, the low level must be held until the completion of the currently executing instruction to generate an interrupt ? bits 1, 0 ? isc01, isc00: interrupt sense control 0 bit 1 and bit 0 the external interrupt 0 is activated by the exte rnal pin int0 if the sreg i-flag and the corre- sponding interrupt mask are set. the level and edges on the external int0 pin that activate the interrupt are defined in table 9-3 . the value on the int0 pin is sampled before detecting edges. if edge or toggle interrupt is selected, pulses that last longer than one clock period will generate an interrupt. shorter pulses are not guaranteed to generate an interrupt. if low level interrupt is selected, the low level must be held until the completion of the currently executing instruction to generate an interrupt. bit 76543210 0x35 (0x55) pud sm1 se sm0 isc11 isc10 isc01 isc00 mcucr read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 table 9-2. interrupt 1 sense control isc11 isc10 description 0 0 the low level of int1 generates an interrupt request. 0 1 any logical change on int1 generates an interrupt request. 1 0 the falling edge of int1 generates an interrupt request. 1 1 the rising edge of int1 generates an interrupt request. table 9-3. interrupt 0 sense control isc01 isc00 description 0 0 the low level of int0 generates an interrupt request. 0 1 any logical change on int0 generates an interrupt request. 1 0 the falling edge of int0 generates an interrupt request. 1 1 the rising edge of int0 generates an interrupt request. 52 8246b?avr?09/11 attiny2313a/4313 9.3.2 gimsk ? general interrupt mask register ? bits 2..0 ? res: reserved bits these bits are reserved and will always read as zero. ? bit 7 ? int1: external interrupt request 1 enable when the int1 bit is set (one) and the i-bit in the status register (sreg) is set (one), the exter- nal pin interrupt is enabled. the interrupt sense control bits (isc11 and isc10) in the external interrupt control register a (eicra) define whether the external interrupt is activated on rising and/or falling edge of the int1 pin or level sens ed. activity on the pin will cause an interrupt request even if int1 is configured as an output. the corresponding interrupt of external interrupt request 1 is executed from the int1 interrupt vector. ? bit 6 ? int0: external interrupt request 0 enable when the int0 bit is set (one) and the i-bit in the status register (sreg) is set (one), the exter- nal pin interrupt is enabled. the interrupt sense control bits (isc01 and isc00) in the external interrupt control register a (eicra) define whether the external interrupt is activated on rising and/or falling edge of the int0 pin or level sens ed. activity on the pin will cause an interrupt request even if int0 is configured as an output. the corresponding interrupt of external interrupt request 0 is executed from the int0 interrupt vector. ? bit 5 ? pcie0: pin change interrupt enable 0 when the pcie0 bit is set (one) and the i-bit in the status register (sreg) is set (one), pin change interrupt 0 is enabled. any change on any enabled pcint7 ..0 pin will cause an interrupt. the corresponding interrupt of pin change interrupt request is executed from the pci0 inter- rupt vector. pcint7..0 pins are enabled individually by the pcmsk0 register. ? bit 4 ? pcie2: pin change interrupt enable 2 when the pcie2 bit is set (one) and the i-bit in the status register (sreg) is set (one), pin change interrupt 2 is enabled. any change on any enabled pcint17..1 1 pin will cause an inter- rupt. the corresponding interrupt of pin change interrupt request is executed from the pci2 interrupt vector. pcint17..11 pins are enabled individually by the pcmsk2 register. ? bit 3 ? pcie1: pin change interrupt enable 1 when the pcie1 bit is set (one) and the i-bit in the status register (sreg) is set (one), pin change interrupt 1 is enabled. any change on any enabled pcint10..8 pin will cause an inter- rupt. the corresponding interrupt of pin change interrupt request is executed from the pci1 interrupt vector. pcint10..8 pins are enabled individually by the pcmsk1 register. bit 76543210 0x3b (0x5b) int1 int0 pcie0 pcie2 pcie1 ? ? ? gimsk read/write r/w r/w r/w r/w r/w r r r initial value 0 0 0 0 0 0 0 0 53 8246b?avr?09/11 attiny2313a/4313 9.3.3 gifr ? general interrupt flag register ? bits 2..0 ? res: reserved bits these bits are reserved and will always read as zero. ? bit 7 ? intf1: external interrupt flag 1 when an edge or logic change on the int1 pin triggers an interrupt request, intf1 becomes set (one). if the i-bit in sreg and the int1 bit in gimsk are set (o ne), the mcu will jump to the cor- responding interrupt vector. the flag is cleared when the interrupt routine is executed. alternatively, the flag can be cleared by writing a logical one to it. this flag is always cleared when int1 is configured as a level interrupt. ? bit 6 ? intf0: external interrupt flag 0 when an edge or logic change on the int0 pin triggers an interrupt request, intf0 becomes set (one). if the i-bit in sreg and the int0 bit in gimsk are set (o ne), the mcu will jump to the cor- responding interrupt vector. the flag is cleared when the interrupt routine is executed. alternatively, the flag can be cleared by writing a logical one to it. this flag is always cleared when int0 is configured as a level interrupt. ? bit 5 ? pcif0: pin change interrupt flag 0 when a logic change on any pcint7..0 pin triggers an interrupt request, pcif becomes set (one). if the i-bit in sreg and the pcie0 bit in gimsk are set (one), the mcu will jump to the corresponding interrupt vector. the flag is cleared when the interrupt routine is executed. alter- natively, the flag can be cleared by writing a logical one to it. ? bit 4 ? pcif2: pin change interrupt flag 2 when a logic change on any pcint17..11 pin triggers an interrupt request, pcif2 becomes set (one). if the i-bit in sreg and the pcie2 bit in gimsk are set (one), the mcu will jump to the corresponding interrupt vector. the flag is cleared when the interrupt routine is executed. alter- natively, the flag can be cleared by writing a logical one to it. ? bit 3 ? pcif1: pin change interrupt flag 1 when a logic change on any pcint10..8 pin triggers an interrupt request, pcif1 becomes set (one). if the i-bit in sreg and the pcie1 bit in gimsk are set (one), the mcu will jump to the corresponding interrupt vector. the flag is cleared when the interrupt routine is executed. alter- natively, the flag can be cleared by writing a logical one to it. 9.3.4 pcmsk2 ? pin change mask register 2 ? bit 7 ? res: reserved bit these bits are reserved and will always read as zero. bit 76543210 0x3a (0x5a) intf1 intf0 pcif0 pcif2 pcif1 ? ? ? gifr read/write r/w r/w r/w r/w r/w r r r initial value 0 0 0 0 0 0 0 0 bit 7654 3 2 1 0 0x05 (0x25) ? pcint17 pcint16 pcint15 pcint14 pcint13 pcint12 pcint11 pcmsk2 read/write r r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 54 8246b?avr?09/11 attiny2313a/4313 ? bits 6..0 ? pcint17..11: pin change enable mask 17..11 each pcint17..11 bit selects whether pin change interrupt is enabled on the corresponding i/o pin. if pcint17..11 is set and the pcie1 bit in gimsk is set, pin change interrupt is enabled on the corresponding i/o pin. if pcint17..11 is cleared, pin change interrupt on the corresponding i/o pin is disabled. 9.3.5 pcmsk1 ? pin change mask register 1 ? bits 7:3 ? res: reserved bits these bits are reserved and will always read as zero. ? bits 2..0 ? pcint10..8: pin change enable mask 10..8 each pcint10..8 bit selects whether pin change interrupt is enabled on the corresponding i/o pin. if pcint10..8 is set and the pcie1 bit in gimsk is set, pin change interrupt is enabled on the corresponding i/o pin. if pcint10..8 is cleared, pin change interrupt on the corresponding i/o pin is disabled. 9.3.6 pcmsk0 ? pin change mask register 0 ? bits 7..0 ? pcint7..0: pin change enable mask 7..0 each pcint7..0 bit selects whether pin change interrupt is enabled on the corresponding i/o pin. if pcint7..0 is set and the pcie0 bit in gimsk is set, pin change interrupt is enabled on the corresponding i/o pin. if pcint7..0 is cleared, pin change interrupt on the corresponding i/o pin is disabled. bit 7 6 5 4 3 2 1 0 0x04 (0x24) ? ? ? ? ? pcint10 pcint9 pcint8 pcmsk1 read/write r r r r r r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 0x20 (0x40) pcint7 pcint6 pcint5 pcint4 pcint3 pcint2 pcint1 pcint0 pcmsk0 read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 55 8246b?avr?09/11 attiny2313a/4313 10. i/o-ports all avr ports have true read-modi fy-write functionality when used as general digital i/o ports. this means that the direction of one port pin can be changed without unintentionally changing the direction of any other pin with the sbi and cbi instructions. the same applies when chang- ing drive value (if configured as output) or enabling/disabling of pull-up resistors (if configured as input). each output buffer has symmetrical drive characteristics with both high sink and source capability. the pin driver is stro ng enough to drive led displays directly. all port pins have indi- vidually selectable pull-up resistors with a suppl y-voltage invariant resistance. all i/o pins have protection diodes to both v cc and ground as indicated in figure 10-1 on page 55 . see ?electri- cal characteristics? on page 198 for a complete list of parameters. figure 10-1. i/o pin equivalent schematic all registers and bit references in this section are written in general form. a lower case ?x? repre- sents the numbering letter for the port, and a lower case ?n? represents the bit number. however, when using the register or bit defines in a progr am, the precise form must be used. for example, portb3 for bit no. 3 in port b, here documented generally as portxn. the physical i/o regis- ters and bit locations are listed in ?register description? on page 69 . three i/o memory address locations are allocated for each port, one each for the data register ? portx, data direction register ? ddrx, and the port input pins ? pinx. the port input pins i/o location is read only, while the data register and the data direction register are read/write. however, writing a logic one to a bit in the pinx register, will result in a toggle in the correspond- ing bit in the data register. in addition, the pu ll-up disable ? pud bit in mcucr disables the pull-up function for all pins in all ports when set. using the i/o port as general digital i/o is described in ?ports as general digital i/o? on page 56 . most port pins are multiplexed with alternate functions for the peripheral features on the device. how each alternate function interferes with the port pin is described in ?alternate port functions? on page 60 . refer to the individual module sectio ns for a full description of the alter- nate functions. note that enabling the alternate function of some of the port pins does not affect the use of the other pins in the port as general digital i/o. c pin logic r pu see figure "general digital i/o" for details pxn 56 8246b?avr?09/11 attiny2313a/4313 10.1 ports as gener al digital i/o the ports are bi-directional i/o ports with optional internal pull-ups. figure 10-2 shows a func- tional description of one i/o-port pin, here generically called pxn. figure 10-2. general digital i/o (1) note: 1. wrx, wpx, wdx, rrx, rpx, and rdx are co mmon to all pins within the same port. clk i/o , sleep, and pud are common to all ports. 10.1.1 configuring the pin each port pin consists of three register bits: ddxn, portxn, and pinxn. as shown in ?register description? on page 69 , the ddxn bits are accessed at the ddrx i/o address, the portxn bits at the portx i/o address, and the pinxn bits at the pinx i/o address. the ddxn bit in the ddrx register selects the direct ion of this pin. if ddxn is written logic one, pxn is configured as an output pin. if ddxn is written logic zero, pxn is configured as an input pin. if portxn is written logic one when the pin is c onfigured as an input pin, the pull-up resistor is activated. to switch the pull-up resistor off, portxn has to be written logic zero or the pin has to be configured as an output pin. the port pins are tri-stated when reset condition becomes active, even if no clocks are running. if portxn is written logic one when the pin is conf igured as an output pin, the port pin is driven high (one). if portxn is written logic zero when the pin is configured as an output pin, the port pin is driven low (zero). clk rpx rrx rdx wdx pud synchronizer wdx: write ddrx wrx: write portx rrx: read portx register rpx: read portx pin pud: pullup disable clk i/o : i/o clock rdx: read ddrx d l q q reset reset q q d q q d clr portxn q q d clr ddxn pinxn data b u s sleep sleep: sleep control pxn i/o wpx 0 1 wrx wpx: write pinx register 57 8246b?avr?09/11 attiny2313a/4313 10.1.2 toggling the pin writing a logic one to pinxn toggles the value of portxn, independent on the value of ddrxn. note that the sbi instruction can be used to toggle one single bit in a port. 10.1.3 switching between input and output when switching between tri-state ({ddxn, portxn} = 0b00) and output high ({ddxn, portxn} = 0b11), an intermediate state with either pull-up enabled {ddxn, portxn} = 0b01) or output low ({ddxn, portxn} = 0b10) must occur. norma lly, the pull-up enabled state is fully accept- able, as a high-impedant enviro nment will not notice the differenc e between a strong high driver and a pull-up. if this is not the case, the pud bit in the mcucr register can be set to disable all pull-ups in all ports. switching between input with pull-up and output low generates the same problem. the user must use either the tri-state ({ddxn, portxn} = 0b00) or the output high state ({ddxn, portxn} = 0b10) as an intermediate step. table 10-1 summarizes the control signals for the pin value. 10.1.4 reading the pin value independent of the setting of data direction bit ddxn, the port pin can be read through the pinxn register bit. as shown in figure 10-2 on page 56 , the pinxn register bit and the preced- ing latch constitute a synchronizer. this is needed to avoid metastability if the physical pin changes value near the edge of the internal clock, but it also introduces a delay. figure 10-3 shows a timing diagram of the synchronization when reading an externally applied pin value. the maximum and minimum propagation delays are denoted t pd,max and t pd,min respectively. figure 10-3. synchronization when reading an externally applied pin value table 10-1. port pin configurations ddxn portxn pud (in mcucr) i/o pull-up comment 0 0 x input no tri-state (hi-z) 0 1 0 input yes pxn will source current if ext. pulled low 0 1 1 input no tri-state (hi-z) 1 0 x output no output low (sink) 1 1 x output no output high (source) xxx in r17, pinx 0x00 0xff instructions sync latch pinxn r17 xxx system clk t pd, max t pd, min 58 8246b?avr?09/11 attiny2313a/4313 consider the clock period starting shortly after the first falling edge of the system cl ock. the latch is closed when the clock is low, and goes transpa rent when the clock is high, as indicated by the shaded region of the ?sync latch? signal. the signal value is latched when the system clock goes low. it is clocked into the pinxn register at the succeeding positive clock edge. as indi- cated by the two arrows tpd,max and tpd,min, a single signal tr ansition on the pin will be delayed between ? and 1? system clock period depending upon the time of assertion. when reading back a software assigned pin value, a nop instruction must be inserted as indi- cated in figure 10-4 on page 58 . the out instruction sets the ?sync latch? signal at the positive edge of the clock. in this case, the delay tpd through the synchronizer is one system clock period. figure 10-4. synchronization when reading a software assigned pin value 10.1.5 digital input enable and sleep modes as shown in figure 10-2 on page 56 , the digital input signal can be clamped to ground at the input of the schmitt-trigger. th e signal denoted sleep in the fi gure, is set by the mcu sleep controller in power-down and standby modes to avoid high power consumption if some input signals are left floating, or have an analog signal level close to v cc /2. sleep is overridden for port pins enabled as ex ternal interrupt pins. if the external interrupt request is not e nabled, sleep is active also for these pins. sl eep is also overri dden by various other alternate functions as described in ?alternate port functions? on page 60 . if a logic high level (?one?) is present on an asynchronous external interrupt pin configured as ?interrupt on rising edge, falling edge, or any logic change on pin? while the external interrupt is not enabled, the corresponding external interrupt flag will be set when resuming from the above mentioned sleep mode, as the clamping in these sleep mode produces the requested logic change. 10.1.6 unconnected pins if some pins are unused, it is recommended to ens ure that these pins have a defined level. even though most of the digital inputs are disabled in the deep sleep modes as described above, float- ing inputs should be avoided to reduce current consumption in all other modes where the digital inputs are enabled (reset, active mode and idle mode). the simplest method to ensure a defined level of an unused pin, is to enable the internal pull-up. in this case, the pull-up will be disabled during reset. if low po wer consumption during reset is out portx, r16 nop in r17, pinx 0xff 0x00 0xff system clk r16 instructions sync latch pinxn r17 t pd 59 8246b?avr?09/11 attiny2313a/4313 important, it is recommended to use an external pull-up or pulldown. connecting unused pins directly to v cc or gnd is not recommended, since this ma y cause excessive curr ents if the pin is accidentally configured as an output. 10.1.7 program examples the following code example shows how to set port a pins 0 and 1 high, 2 and 3 low, and define the port pins from 4 to 7 as input with a pull-up assigned to port pin 4. the resulting pin values are read back again, but as previously discussed, a nop instruction is included to be able to read back the value recently assigned to some of the pins. note: two temporary registers are used to minimize the time from pull-ups are set on pins 0, 1 and 4, until the direction bits are correctly set, defining bit 2 and 3 as low and redefining bits 0 and 1 as strong high drivers. note: 1. see ?code examples? on page 7. assembly code example ... ; define pull-ups and set outputs high ; define directions for port pins ldi r16,(1< 61 8246b?avr?09/11 attiny2313a/4313 table 10-2 summarizes the function of the overriding signals. the pin and port indexes from fig- ure 10-5 are not shown in the succeeding tables. the overriding signals are generated internally in the modules having the alternate function. the following subsections shortly describe the alternate functions for each port, and relate the overriding signals to the alternate function. refer to the alternate function description for further details. table 10-2. generic description of overriding signals for alternate functions signal name full name description puoe pull-up override enable if this signal is set, the pull-u p enable is controlled by the puov signal. if this signal is cleared, the pull-up is enabled when {ddxn, portxn, pud} = 0b010. puov pull-up override value if puoe is set, the pull-up is enabled/disabled when puov is set/cleared, regardless of the setting of the ddxn, portxn, and pud register bits. ddoe data direction override enable if this signal is set, the output driver enable is controlled by the ddov signal. if this signal is cleared, the output driver is enabled by the ddxn register bit. ddov data direction override value if ddoe is set, the output dr iver is enabled/disabled when ddov is set/cleared, regardless of the setting of the ddxn register bit. pvoe port value override enable if this signal is set and the output driver is enabled, the port value is controlled by the pvov signal. if pvoe is cleared, and the output driver is enabled, the port value is controlled by the portxn register bit. pvov port value override value if pvoe is set, the port value is set to pvov, regardless of the setting of the portxn register bit. ptoe port toggle override enable if ptoe is set, the portxn register bit is inverted. dieoe digital input enable override enable if this bit is set, the digital in put enable is controlled by the dieov signal. if this signal is cleared, the digital input enable is determined by mcu state (normal mode, sleep mode). dieov digital input enable override value if dieoe is set, the digital input is enabled/disabled when dieov is set/cleared, regardless of the mcu state (normal mode, sleep mode). di digital input this is the digital input to altern ate functions. in the figure, the signal is connected to the out put of the schmitt-trigger but before the synchronizer. unless the digital input is used as a clock source, the module with the alternate function will use its own synchronizer. aio analog input/output this is the analog input/output to/from alternate functions. the signal is connected directly to the pad, and can be used bi- directionally. 62 8246b?avr?09/11 attiny2313a/4313 10.2.1 alternate functions of port a the port a pins with alternate function are shown in table 10-3 . ? port a, bit 0 ? xtal1/clki/pcint8 ? xtal1: chip clock oscillator pin 1. used fo r all chip clock sources except internal calibratable rc oscillator. when used as a clock pin, the pin can not be used as an i/o pin. when using internal calibrata ble rc oscillator as a chip clock source, pa0 serves as an ordinary i/o pin. ? clki: clock input from an external clock source, see ?external clock? on page 27 . ? pcint8: pin change interrupt source 8. the pa0 pin can serve as an external interrupt source for pin change interrupt 1. ? port a, bit 1 ? xtal2/pcint9 ? xtal2: chip clock oscillator pin 2. used as clock pin for all chip clock sources except internal calibratable rc oscillator and external clock. when used as a clock pin, the pin can not be used as an i/o pin. when using internal calibratable rc oscillator or external clock as a chip clock sources, pa1 serves as an ordinary i/o pin. ? pcint9: pin change interrupt source 9. the pa1 pin can serve as an external interrupt source for pin change interrupt 1. ? port a, bit 2 ? reset /dw/pcint10 ? reset : external reset input is active low and enabled by unprogramming (?1?) the rstdisbl fuse. pullup is activated and output driver and digital input are deactivated when the pin is used as the reset pin. ? dw: when the debugwire enable (dwen) fuse is programmed and lock bits are unprogrammed, the debugwire system within th e target device is activated. the reset port pin is configured as a wire-and (open-dr ain) bi-directional i/o pin with pull-up enabled and becomes the communication gateway between target and emulator. ? pcint10: pin change interrupt source 10. the pa2 pin can serve as an external interrupt source for pin change interrupt 1. table 10-3. port a pins alternate functions port pin alternate function pa 0 xtal1: crystal oscillator input clki: external clock input pcint8: pin change interrupt 1, source 8 pa 1 xtal2: crystal oscillator output pcint9: pin change interrupt 1, source 9 pa 2 reset : reset pin dw: debugwire i/o pcint10:pin change interrupt 1, source 10 63 8246b?avr?09/11 attiny2313a/4313 table 10-4 relates the alternate functions of port a to the overriding signals shown in figure 10- 5 on page 60 . notes: 1. rstdisbl is 1 when the fuse is ?0? (programmed). 2. debugwire is enabled when dwen fuse is programmed and lock bits are unprogrammed. 3. ext_osc = crystal oscillator or low frequency cr ystal oscillator is selected as system clock. 4. ext_clock = external closk is selected as system clock. 10.2.2 alternate functions of port b the port b pins with alternate function are shown in table 10-5 . table 10-4. overriding signals for alternate functions in pa2..pa0 signal name pa2/reset/dw/pcint10 pa1/x tal2/pcint9 pa0 /xtal1/pcint8 puoe rstdisbl (1) + debugwire_enable (2) ext_osc (3) ext_clock (4) + ext_osc (3) puov 1 0 0 ddoe rstdisbl (1) + debugwire_enable (2) ext_osc (3) ext_clock (4) + ext_osc (3) ddov debugwire_enable (2) ? debugwire transmit 00 pvoe rstdisbl (1) + debugwire_enable (2) ext_osc (3) ext_clock (4) + ext_osc (3) pvov 0 0 0 ptoe 0 0 0 dieoe rstdisbl (1) + debugwire_enable (2) + pcint10 ? pcie1 ext_osc (3) + pcint9 ? pcie1 ext_clock (4) + ext_osc (3) + (pcint8 ? pcie1) dieov debugwire_enable (2) + (rstdisbl (1) ? pcint10 ? pcie1) ext_osc (3) + pcint9 ? pcie1 (ext_clock (4) ? pwr_down ) + (ext_cloc k (4) ? ext_osc (3) ? pcint8 ? pcie1) di dw/pcint10 input pcint 9 input clki/pcint8 input aio xtal2 xtal1 table 10-5. port b pins alternate functions port pin alternate function pb0 ain0: analog comparator, positive input pcint0:pin change interrupt 0, source 0 pb1 ain1: analog comparator, negative input pcint1: pin change interrupt 0, source 1 pb2 oc0a:: timer/counter0 compare match aoutput pcint2: pin change interrupt 0, source 2 pb3 oc1a: timer/counter1 compare match a output pcint3: pin change interrupt 0, source 3 64 8246b?avr?09/11 attiny2313a/4313 ? port b, bit 0 ? ain0/pcint0 ? ain0: analog comparator positive input. configure the port pin as input with the internal pull- up switched off to avoid the digital port function from interfering with the function of the analog comparator. ? pcint0: pin change interrupt source 0. the pb0 pin can serve as an external interrupt source for pin change interrupt 0. ? port b, bit 1 ? ain1/pcint1 ? ain1: analog comparator negative input . configure the port pin as input with the internal pull-up switched off to avoid the digital port function from interfering with the function of the analog comparator. ? pcint1: pin change interrupt source 1. the pb1 pin can serve as an external interrupt source for pin change interrupt 0. ? port b, bit 2 ? oc0a/pcint2 ? oc0a: output compare match a output. the pb2 pin can serve as an external output for the timer/counter0 output compare a. the pin has to be configured as an output (ddb2 set (one)) to serve this function. the oc0a pin is also the output pin for the pwm mode timer function. ? pcint2: pin change interrupt source 2. the pb2 pin can serve as an external interrupt source for pin change interrupt 0. ? port b, bit 3 ? oc1a/pcint3 ? oc1a: output compare match a output: the pb3 pin can serve as an external output for the timer/counter1 output compare a. the pin has to be configured as an output (ddb3 set (one)) to serve this function. the oc1a pin is also the output pin for the pwm mode timer function. ? pcint3: pin change interrupt source 3: the pb3 pin can serve as an external interrupt source for pin change interrupt 0. ? port b, bit 4 ? oc1b/pcint4 ? oc1b: output compare match b output: the pb4 pin can serve as an external output for the timer/counter1 output compare b. the pin has to be configured as an output (ddb4 set pb4 oc1b: timer/counter1 compare match b output pcint4: pin change interrupt 0, source 4 pb5 di: usi data input (three wire mode) sda: usi data input (two wire mode) pcint5: pin change interrupt 0, source 5 pb6 do: usi data output (three wire mode) pcint6: pin change interrupt 0, source 6 pb7 usck: usi clock (three wire mode) scl : usi clock (two wire mode) pcint7: pin change interrupt 0, source 7 table 10-5. port b pins alternate functions port pin alternate function 65 8246b?avr?09/11 attiny2313a/4313 (one)) to serve this function. the oc1b pin is also the output pin for the pwm mode timer function. ? pcint4: pin change interrupt source 4. the pb4 pin can serve as an external interrupt source for pin change interrupt 0. ? port b, bit 5 ? di/sda/pcint5 ? di: three-wire mode universal serial interface data input. three-wire mode does not override normal port functions, so pin must be configured as an input. sda: two-wire mode serial interface data. ? pcint5: pin change interrupt source 5. the pb5 pin can serve as an external interrupt source for pin change interrupt 0. ? port b, bit 6 ? do/pcint6 ? do: three-wire mode universal serial interface data output. three-wire mode data output overrides portb6 value and it is driven to the port when data direction bit ddb6 is set (one). however the portb6 bit still controls the pull-up enabling pull-up, if di rection is input and portb6 is set (one). ? pcint6: pin change interrupt source 6. the pb6 pin can serve as an external interrupt source for pin change interrupt 0. ? port b, bit 7 ? usck/scl/pcint7 ? usck: three-wire mode univer sal serial interface clock. ? scl: two-wire mode serial clock for usi two-wire mode. ? pcint7: pin change interrupt source 7. the pb7 pin can serve as an external interrupt source for pin change interrupt 0. 66 8246b?avr?09/11 attiny2313a/4313 table 10-6 and table 10-7 relate the alternate functions of port b to the overriding signals shown in figure 10-5 on page 60 . spi mstr input and spi sl ave output constitute the miso signal, while mosi is divided in to spi mstr output and spi slave input. table 10-6. overriding signals for alternate functions in pb7..pb4 signal name pb7/usck/ scl/pcint7 pb6/do/pcint6 pb5/sda/ di/pcint5 pb4/oc1b/ pcint4 puoe usi_two_wire 0 0 0 puov 0 0 0 0 ddoe usi_two_wire 0 usi_two_wire 0 ddov (usi_scl_hold+ portb7 )?ddb7 0 (sda + portb5 )? ddb5 0 pvoe usi_two_wire ? ddb7 usi_three_wire usi_two_wire ? ddb5 oc1b_pvoe pvov 0 do 0 0oc1b_pvov ptoe usi_ptoe 0 0 0 dieoe (pcint7?pcie) +usisie (pcint6?pcie) (pcint5?pcie) + usisie (pcint4?pcie) dieov 1 1 1 1 di pcint7 input usck input scl input pcint6 input pcint5 input sda input di input pcint4 input aio ? ? ? ? table 10-7. overriding signals for alternate functions in pb3..pb0 signal name pb3/oc1a/ pcint3 pb2/oc0a/ pcint2 pb1/ain1/ pcint1 pb0/ain0/ pcint0 puoe 0 0 0 0 puov 0 0 0 0 ddoe 0 0 0 0 ddov 0 0 0 0 pvoe oc1a_pvoe oc0a_pvoe 0 0 pvov oc1a_pvov oc0a_pvov 0 0 ptoe 0 0 0 0 dieoe (pcint3 ? pcie) (pcint2 ? pcie ) (pcint1 ? pcie) (pcint0 ? pcie) dieov 1 1 1 1 di pcint7 input pcint6 inpu t pcint5 input pcint4 input aio ? ? ain1 ain0 67 8246b?avr?09/11 attiny2313a/4313 10.2.3 alternate functions of port d the port d pins with alternate functions are shown in table 10-8 .. ? port d, bit 0 ? rxd/pcint11 ? rxd: uart data receiver. ? pcint11: pin change interrupt source 11. the pd0 pin can serve as an external interrupt source for pin change interrupt 2. ? port d, bit 1 ? txd/pcint12 ? txd: uart data transmitter. ? pcint12: pin change interrupt source 12. the pd1 pin can serve as an external interrupt source for pin change interrupt 2. ? port d, bit 2 ? int0/xck/ckout/pcint13 ? int0: external interrupt source 0. the pd2 pin can serve as en external interrupt source to the mcu. ? xck: usart transfer clock used only by synchronous transfer mode. ? ckout: system clock output. ? pcint13: pin change interrupt source 13. the pd2 pin can serve as an external interrupt source for pin change interrupt 2. ? port d, bit 3 ? int1/pcint14 ? int1: external interrupt source 1. the pd3 pin can serve as an external interrupt source to the mcu. ? pcint14: pin change interrupt source 14. the pd3 pin can serve as an external interrupt source for pin change interrupt 2. table 10-8. port d pins alternate functions port pin alternate function pd0 rxd: uart data receiver pcint11:pin change interrupt 2, source 11 pd1 txd: uart data transmitter pcint12:pin change interrupt 2, source 12 pd2 int0: external interrupt 0 input xck: usart transfer clock ckout: system clock output pcint13:pin change interrupt 2, source 13 pd3 int1: external interrupt 1 input pcint14:pin change interrupt 2, source 14 pd4 t0: timer/counter0 clock source pcint15:pin change interrupt 2, source 15 pd5 oc0b: timer/counter0 compare match b output t1: timer/counter1 clock source pcint16:pin change interrupt 2, source 16 pd6 icpi: timer/counter1 input capture pin pcint17:pin change interrupt 2, source 17 68 8246b?avr?09/11 attiny2313a/4313 ? port d, bit 4 ? t0/pcint15 ? t0: timer/counter0 external counter clock input is enabled by setting (one) the bits cs02 and cs01 in the timer/counte r0 control register (tccr0). ? pcint15: pin change interrupt source 15. the pd4 pin can serve as an external interrupt source for pin change interrupt 2. ? port d, bit 5 ? oc0b/t1/pcint16 ? oc0b: output compare match b output: the pd5 pin can serve as an external output for the timer/counter0 output compare b. the pin has to be configured as an output (ddd5 set (one)) to serve this function. the oc0b pin is also the output pin for the pwm mode timer function. ? t1: timer/counter1 external counter clock input is enabled by setting (one) the bits cs02 and cs01 in the timer/counte r1 control register (tccr1). ? pcint16: pin change interrupt source 16. the pd5 pin can serve as an external interrupt source for pin change interrupt 2. ? port d, bit 6 ? icpi/pcint17 ? icpi: timer/counter1 input capture pin. the pd6 pin can act as an input capture pin for timer/counter1. ? pcint17: pin change interrupt source 17. the pd6 pin can serve as an external interrupt source for pin change interrupt 2. table 10-9 and table 10-10 relates the alternate functions of port d to the overriding signals shown in figure 10-5 on page 60 . table 10-9. overriding signals for alternate functions pd6..pd4 signal name pd6/icpi/pcint17 pd5/oc1b /t1/pcint16 pd4/t0/pcint15 puoe000 puov000 ddoe 0 0 0 ddov 0 0 0 pvoe 0 oc1b_pvoe 0 pvov 0 oc1b_pvov 0 ptoe000 dieoe icpi enable + pcint17 t1 enable + pcint16 t0 enable + pcint15 dieov pcint17 pcint16 pcint15 di icpi input/pcint17 t1 inpu t/pcint16 t0 input/pcint15 aio??ain1 69 8246b?avr?09/11 attiny2313a/4313 10.3 register description 10.3.1 mcucr ? mcu control register ? bit 7 ? pud: pull-up disable when this bit is written to one, the pull-ups in the i/o ports are disabled even if the ddxn and portxn registers are configured to enable the pull-ups ({ddxn, portxn} = 0b01). see ?con- figuring the pin? on page 56 for more details about this feature. 10.3.2 porta ? port a data register 10.3.3 ddra ? port a data direction register table 10-10. overriding signals for alternate functions in pd3..pd0 signal name pd3/int1/ pcint14 pd2/int0/xck/ckout/ pcint13 pd1/txd/ pcint12 pd0/rxd/pcint11 puoe 0 0 txd_oe rxd_oe puov00 0portd0 ? pud ddoe 0 0 txd_oe rxd_en ddov 0 0 1 0 pvoe 0 xcko_pvoe txd_oe 0 pvov 0 xcko_pvov txd_pvov 0 ptoe00 00 dieoe int1 enable + pcint14 int0 enable/ xck input enable/pcint13 pcint12 pcint11 dieov pcint14 pcint13 pcint12 pcint11 di int1 input/ pcint14 int0 input/xck input/ pcint13 pcint12 rxd input/pcint11 aio ? ? ? ? bit 7 6 5 4 3 2 1 0 0x35 (0x55) pud sm1 se sm0 isc11 isc10 isc01 isc00 mcucr read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 0x1b (0x3b) ?????porta2porta1porta0 porta read/write rrrrrr/wr/wr/w initial value00000000 bit 76543210 0x1a (0x3a) ????? dda2 dda1 dda0 ddra read/write rrrrrr/wr/wr/w initial value00000000 70 8246b?avr?09/11 attiny2313a/4313 10.3.4 pina ? port a input pins address 10.3.5 portb ? port b data register 10.3.6 ddrb ? port b data direction register 10.3.7 pinb ? port b input pins address 10.3.8 portd ? port d data register 10.3.9 ddrd ? port d data direction register 10.3.10 pind ? port d input pins address bit 76543210 0x19 (0x39) ????? pina2 pina1 pina0 pina read/writerrrrrr/wr/wr/w initial value n/a n/a n/a n/a n/a n/a n/a n/a bit 76543210 0x18 (0x38) portb7 portb6 portb5 portb4 portb3 portb2 portb1 portb0 portb read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 0x17 (0x37) ddb7 ddb6 ddb5 ddb4 ddb3 ddb2 ddb1 ddb0 ddrb read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 0x16 (0x36) pinb7 pinb6 pinb5 pinb4 pi nb3 pinb2 pinb1 pinb0 pinb read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value n/a n/a n/a n/a n/a n/a n/a n/a bit 76543210 0x12 (0x32) ? portd6 portd5 portd4 portd3 portd2 portd1 portd0 portd read/write r r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 0x11 (0x31) ? ddd6 ddd5 ddd4 ddd3 ddd2 ddd1 ddd0 ddrd read/write r r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 0x10 (0x30) ? pind6 pind5 pind4 pind3 pind2 pind1 pind0 pind read/write r r/w r/w r/w r/w r/w r/w r/w initial value n/a n/a n/a n/a n/a n/a n/a n/a 71 8246b?avr?09/11 attiny2313a/4313 11. 8-bit timer/counter0 with pwm 11.1 features ? two independent output compare units ? double buffered outp ut compare registers ? clear timer on compare match (auto reload) ? glitch free, phase correct pulse width modulator (pwm) ? variable pwm period ? frequency generator ? three independent interrupt sources (tov0, ocf0a, and ocf0b) 11.2 overview timer/counter0 is a general purpose 8-bit time r/counter module, with two independent output compare units, and with pwm support. it allows accurate program execution timing (event man- agement) and wave generation. a simplified block diagram of the 8-bit timer/counter is shown in figure 11-1 . for the actual placement of i/o pins, refer to ?pinout attiny2313a/4313? on page 2 . cpu accessible i/o regis- ters, including i/o bits and i/o pins, are shown in bold. the device-specific i/o register and bit locations are listed in the ?register description? on page 82 . figure 11-1. 8-bit timer/counter block diagram 11.2.1 registers the timer/counter (tcnt0) and output compare registers (ocr0a and ocr0b) are 8-bit registers. interrupt request (abbreviated to int.req . in the figure) signals are all visible in the timer interrupt flag register (tif r). all interrupts are individually masked with the timer inter- rupt mask register (timsk). tifr and timsk are not shown in the figure. the timer/counter can be clocked internally, via the prescaler, or by an external clock source on the t0 pin. the clock select logic block controls which clock source and edge the timer/counter clock select timer/counter data bus ocrna ocrnb = = tcntn waveform generation waveform generation ocfna ocfnb = fixed top value control logic = 0 top bottom count clear direction tovn (int.req.) ocfna (int.req.) ocfnb (int.req.) tccrna tccrnb tn edge detector ( from prescaler ) clk tn 72 8246b?avr?09/11 attiny2313a/4313 uses to increment (or decrement) its value. the timer/counter is inactive when no clock source is selected. the output from the clock select logic is referred to as the timer clock (clk t0 ). the double buffered output compare registers (ocr0a and ocr0b) is compared with the timer/counter value at all times. the result of the compare can be used by the waveform gen- erator to generate a pwm or variable frequency output on the output compare pins (oc0a and oc0b). see ?output compare unit? on page 73. for details. the comp are match event will also set the compare flag (ocf0a or ocf0b) which can be used to generate an output compare interrupt request. 11.2.2 definitions many register and bit references in this section are written in general form. a lower case ?n? replaces the timer/counter number, in this case 0. a lower case ?x? replaces the output com- pare unit, in this case compare unit a or compare unit b. howe ver, when using the register or bit defines in a program, the precise form must be used, i.e., tcnt0 for accessing timer/counter0 counter value and so on. the definitions in table 11-1 are also used extensively throughout the document. 11.3 clock sources the timer/counter can be clocked by an internal or an external clock source. the clock source is selected by the clock select logic which is controlled by the clock select (cs02:0) bits located in the timer/counter control register (tccr0b). for details on clock sources and pres- caler, see ?timer/counter0 and timer/counter1 prescalers? on page 118 . 11.4 counter unit the main part of the 8-bit timer/counter is the programmable bi-directional counter unit. figure 11-2 shows a block diagram of the counter and its surroundings. figure 11-2. counter unit block diagram table 11-1. definitions constant description bottom the counter reaches bottom when it becomes 0x00 max the counter reaches its maximum when it becomes 0xff (decimal 255) top the counter reaches the top when it become s equal to the highest value in the count sequence. the top value can be assigned to be the fixed value 0xff (max) or the value stored in the ocr0a register. the assi gnment depends on the mode of operation data bus tcntn control logic count tovn (int.req.) clock select top tn edge detector ( from prescaler ) clk tn bottom direction clear 73 8246b?avr?09/11 attiny2313a/4313 signal description (internal signals): count increment or decrement tcnt0 by 1. direction select between increment and decrement. clear clear tcnt0 (set all bits to zero). clk t n timer/counter clock, referred to as clk t0 in the following. top signalize that tcnt0 has reached maximum value. bottom signalize that tcnt0 has re ached minimum value (zero). depending of the mode of operation used, the counter is cleared, incremented, or decremented at each timer clock (clk t0 ). clk t0 can be generated from an external or internal clock source, selected by the clock select bits (cs02:0). w hen no clock source is selected (cs02:0 = 0) the timer is stopped. however, the tcnt0 value can be accessed by the cpu, regardless of whether clk t0 is present or not. a cpu write overrides (has priority over) all counter clear or count operations. the counting sequence is determined by the setting of the wgm01 and wgm00 bits located in the timer/counter control register (tccr0a) and the wgm02 bit located in the timer/counter control register b (tccr0b). there are clos e connections between how the counter behaves (counts) and how waveforms are generated on the output compare output oc0a. for more details about advanced counting sequences and waveform generation, see ?modes of opera- tion? on page 97 . the timer/counter overflow flag (tov0) is set according to the mode of operation selected by the wgm01:0 bits. tov0 can be used for generating a cpu interrupt. 11.5 output compare unit the 8-bit comparator continuously compares tcnt0 with the output compare registers (ocr0a and ocr0b). whenever tcnt0 equals ocr0a or ocr0b, the comparator signals a match. a match will set the output compare flag (ocf0a or ocf0 b) at the next timer clock cycle. if the corresponding interrupt is enabled, the output compare flag generates an output compare interrupt. the output compare flag is automatically cleared when the interrupt is exe- cuted. alternatively, the flag can be cleared by software by writing a logical one to its i/o bit location. the waveform generator uses the matc h signal to generate an output according to operating mode set by the wgm02:0 bits and compare output mode (com0x1:0) bits. the max and bottom signals are used by the waveform generator for handling the special cases of the extreme values in some modes of operation (see ?modes of operation? on page 97 ). figure 11-3 shows a block diagram of the output compare unit. 74 8246b?avr?09/11 attiny2313a/4313 figure 11-3. output compare unit, block diagram the ocr0x registers are double buffered when using any of the pulse width modulation (pwm) modes. for the normal and clear timer on compare (ctc) modes of operation, the dou- ble buffering is disabled. the double buffering synchronizes the update of the ocr0x compare registers to either top or bottom of the counting sequence. the synchronization prevents the occurrence of odd-length, non-symmetrical pwm pulses, thereby making the output glitch-free. the ocr0x register access may seem complex, but this is not case. when the double buffering is enabled, the cpu has access to the ocr0x buffer register, and if double buffering is dis- abled the cpu will access the ocr0x directly. 11.5.1 force output compare in non-pwm waveform generation modes, the match output of the comparator can be forced by writing a one to the force outp ut compare (foc0x) bit. forcin g compare match will not set the ocf0x flag or reload/clear the timer, but the oc0x pin will be updated as if a real compare match had occurred (the com0x1:0 bits settings de fine whether the oc0x pin is set, cleared or toggled). 11.5.2 compare match bloc king by tcnt0 write all cpu write operations to the tcnt0 register will block any compare ma tch that occur in the next timer clock cycle, even when the timer is stopped. this feature allows ocr0x to be initial- ized to the same value as tcnt0 without triggering an interrupt when the timer/counter clock is enabled. 11.5.3 using the output compare unit since writing tcnt0 in any mo de of operation will block all compare matches for one timer clock cycle, there are risks involved when ch anging tcnt0 when using the output compare unit, independently of whether the timer/counter is running or not. if the value written to tcnt0 equals the ocr0x value, the compare match will be missed, resulting in incorrect waveform ocfn x (int.req.) = (8-bit comparator ) ocrnx ocnx data bus tcntn wgmn1:0 waveform generator top focn comnx1:0 bottom 75 8246b?avr?09/11 attiny2313a/4313 generation. similarly, do not write the tcnt0 value equal to bottom when the counter is down-counting. the setup of the oc0x should be performed before setting the data direction register for the port pin to output. the easiest way of setting the oc0x value is to use the force output com- pare (foc0x) strobe bits in normal mode. the oc0x registers keep their values even when changing between waveform generation modes. be aware that the com0x1:0 bits are not doubl e buffered together with the compare value. changing the com0x1:0 bits will take effect immediately. 11.6 compare match output unit the compare output mode (com0x1:0) bits have two functions. the waveform generator uses the com0x1:0 bits for defining the output compare (oc0x) state at the next compare match. also, the com0x1:0 bits control the oc0x pin output source. figure 11-4 shows a simplified schematic of the logic affected by the com0x1:0 bit setting. the i/o registers, i/o bits, and i/o pins in the figure are shown in bold. only the parts of the general i/o port control registers (ddr and port) that are affected by the com0x1:0 bits are shown. when referring to the oc0x state, the reference is for the internal oc0x register, not the oc0x pin. if a system reset occur, the oc0x register is reset to ?0?. figure 11-4. compare match output unit, schematic the general i/o port function is overridden by the output compare (oc0x) from the waveform generator if either of the com0x1:0 bits are set. however, the oc0x pin direction (input or out- put) is still controlled by the da ta direction register (ddr) for th e port pin. the data direction register bit for the oc0x pin (ddr_oc0x) must be set as output before the oc0x value is visi- ble on the pin. the port override function is independent of the waveform generation mode. the design of the output compare pin logic allows initialization of the oc0x state before the out- put is enabled. note that some com0x1:0 bi t settings are reserved for certain modes of operation. see ?register description? on page 82. port ddr dq dq ocn pin ocnx dq waveform generator comnx1 comnx0 0 1 data bus focn clk i/o 76 8246b?avr?09/11 attiny2313a/4313 11.6.1 compare output mode and waveform generation the waveform generator uses the com0x1:0 bits differently in normal, ctc, and pwm modes. for all modes, setting the com0x1:0 = 0 tells the waveform generator that no action on the oc0x register is to be performed on the next compare match. for compare output actions in the non-pwm modes refer to figure 11-3 on page 74 . for fast pwm mode, refer to table 10-6 on page 66 , and for phase correct pwm refer to table 10-7 on page 66 . a change of the com0x1:0 bits state will have effe ct at the first compare match after the bits are written. for non-pwm modes, the action can be fo rced to have immediate effect by using the foc0x strobe bits. 11.7 modes of operation the mode of operation, i.e., the behavior of the timer/counter and the output compare pins, is defined by the combination of the waveform generation mode (wgm02:0) and compare output mode (com0x1:0) bits. the compare output mode bits do not affect the counting sequence, while the waveform generation mode bits do. the com0x1:0 bits control whether the pwm out- put generated should be inverted or not (inverted or non-inverted pwm). for non-pwm modes the com0x1:0 bits control whether the output should be set, cleared, or toggled at a compare match ( see ?compare match output unit? on page 75. ). for detailed timing information refer to figure 11-8 , figure 11-9 , figure 11-10 and figure 11-11 in ?timer/counter timing diagrams? on page 80 . 11.7.1 normal mode the simplest mode of operation is the normal mode (wgm02:0 = 0). in this mode the counting direction is always up (incrementing), and no counter clear is performed. the counter simply overruns when it passes its maximum 8-bit value (top = 0xff) and then restarts from the bot- tom (0x00). in normal o peration the timer/counter overflow flag (tov0) will be set in the same timer clock cycle as the tcnt0 becomes zero. the tov0 flag in this case behaves like a ninth bit, except that it is only set, not cleared. however, combined with the timer overflow interrupt that automatically clears the tov0 flag, the timer resolution can be increased by software. there are no special cases to consider in the normal mode, a new counter value can be written anytime. the output compare unit can be used to generate interrupts at some given time. using the out- put compare to generate waveforms in normal mode is not recommended, since this will occupy too much of the cpu time. 11.7.2 clear timer on compare match (ctc) mode in clear timer on compare or ctc mode (wgm 02:0 = 2), the ocr0a register is used to manipulate the counter resolution. in ctc mode the counter is cleared to zero when the counter value (tcnt0) matches the ocr0a. the ocr0a defines the top value for the counter, hence also its resolution. this mode allows greater control of the compare match output frequency. it also simplifies the operation of counting external events. the timing diagram for the ctc mode is shown in figure 11-5 . the counter value (tcnt0) increases until a compare match occurs between tcnt0 and ocr0a, and then counter (tcnt0) is cleared. 77 8246b?avr?09/11 attiny2313a/4313 figure 11-5. ctc mode, timing diagram an interrupt can be generated each time the counter value reaches the top value by using the ocf0a flag. if the interrupt is enabled, the interrupt handler routine can be used for updating the top value. however, changing top to a va lue close to bottom when the counter is run- ning with none or a low prescaler value must be done with care since the ctc mode does not have the double buffering feature. if the new value written to ocr0a is lower than the current value of tcnt0, the counter will miss the compar e match. the counter will then have to count to its maximum value (0xff) and wrap around starting at 0x00 before the compare match can occur. for generating a waveform output in ctc mode, the oc0a output can be set to toggle its logical level on each compare match by setting the compare output mode bits to toggle mode (com0a1:0 = 1). the oc0a value will not be visible on the port pin unless the data direction for the pin is set to output. the waveform ge nerated will have a ma ximum frequency of f oc0 = f clk_i/o /2 when ocr0a is set to zero (0x00). the waveform frequency is defined by the following equation: the n variable represents the prescale factor (1, 8, 64, 256, or 1024). as for the normal mode of operation, the tov0 flag is set in the same timer clock cycle that the counter counts from max to 0x00. 11.7.3 fast pwm mode the fast pulse width modulation or fast pwm mode (wgm02:0 = 3 or 7) provides a high fre- quency pwm waveform generation option. the fast pwm differs from the other pwm option by its single-slope operation. the counter counts from bottom to top then restarts from bot- tom. top is defined as 0xff when wgm2:0 = 3, and ocr0a when wgm2:0 = 7. in non- inverting compare output mode, the output compare (oc0x) is cleared on the compare match between tcnt0 and ocr0x, and set at bottom. in inverting compare output mode, the out- put is set on compare match and cleared at bottom. due to the single-slope operation, the operating frequency of the fast pwm mode can be twice as high as the phase correct pwm mode that use dual-slope operation. this high frequency makes the fast pwm mode well suited for power regulation, rectification, and dac app lications. high frequency a llows physically small sized external components (coils, capacitors), and therefore reduces total system cost. in fast pwm mode, the counter is incremented until the counter value matches the top value. the counter is then cleared at the following timer clock cycle. the timing diagram for the fast tcntn ocn (toggle) ocnx interrupt flag set 1 4 period 2 3 (comnx1:0 = 1) f ocnx f clk_i/o 2 n 1 ocrnx + () ?? ------------------------------------------------- - = 78 8246b?avr?09/11 attiny2313a/4313 pwm mode is shown in figure 11-4 . the tcnt0 value is in the timing diagram shown as a his- togram for illustrating the single-slope operation. the diagram includes non-inverted and inverted pwm outputs. the small horizontal li ne marks on the tcnt0 slopes represent com- pare matches between ocr0x and tcnt0. figure 11-6. fast pwm mode, timing diagram the timer/counter overflow flag (tov0) is set each time the counter reaches top. if the inter- rupt is enabled, the interrupt handler routine can be used for updating the compare value. in fast pwm mode, the compare unit allows generation of pwm waveforms on the oc0x pins. setting the com0x1:0 bits to two will produce a non-inverted pwm and an inverted pwm output can be generated by setting the com0x1:0 to three: setting the com0a1:0 bits to one allows the ac0a pin to toggle on compare matches if t he wgm02 bit is set. this option is not available for the oc0b pin (see table 10-6 on page 66 ). the actual oc0x value will only be visible on the port pin if the data direction for the port pin is set as output. the pwm waveform is generated by setting (or clearing) the oc0x register at the compare match between ocr0x and tcnt0, and clearing (or setting) the oc0x register at t he timer clock cycle the counter is cleared (changes from top to bottom). the pwm frequency for the output can be calculated by the following equation: the n variable represents the prescale factor (1, 8, 64, 256, or 1024). the extreme values for the ocr0a register represents special cases when generating a pwm waveform output in the fast pwm mode. if the ocr0a is set equal to bottom, the output will be a narrow spike for each max+1 timer clock cycle. setting the ocr0a equal to max will result in a constantly high or low output (depending on the polarity of the output set by the com0a1:0 bits.) a frequency (with 50% duty cycle) waveform output in fast pwm mode can be achieved by set- ting oc0x to toggle its logical level on each compare match (com0x1:0 = 1). the waveform generated will have a maximum frequency of f oc0 = f clk_i/o /2 when ocr0a is set to zero. this tcntn ocrnx update and tovn interrupt flag set 1 period 2 3 ocn ocn (comnx1:0 = 2) (comnx1:0 = 3) ocrnx interrupt flag set 4 5 6 7 f ocnxpwm f clk_i/o n 256 ? ------------------ = 79 8246b?avr?09/11 attiny2313a/4313 feature is similar to the oc0a toggle in ctc mode, except the double buffer feature of the out- put compare unit is enabled in the fast pwm mode. 11.7.4 phase correct pwm mode the phase correct pwm mode (wgm02:0 = 1 or 5) provides a high resolution phase correct pwm waveform generation option. the phase correct pwm mode is based on a dual-slope operation. the counter counts repeatedly from bottom to top and then from top to bot- tom. top is defined as 0xff when wgm2:0 = 1, and ocr0a when wgm2:0 = 5. in non- inverting compare output mode, the output compare (oc0x) is cleared on the compare match between tcnt0 and ocr0x while upcounting, and set on the compare match while down- counting. in inverting output compare mode, the operation is inverted. the dual-slope operation has lower maximum operation frequency than single slope operation. however, due to the sym- metric feature of the dual-slope pwm modes, these modes are preferred for motor control applications. in phase correct pwm mode the counter is incremented until the counter value matches top. when the counter reaches top, it changes the count direction. the tcnt0 value will be equal to top for one timer clock cycle. the timing diagram for the phase correct pwm mode is shown on figure 11-7 . the tcnt0 value is in the timing diagram shown as a histogram for illustrating the dual-slope operation. the diagram includes non-inverted and inverted pwm outputs. the small horizontal line marks on the tcnt0 slop es represent compare matches between ocr0x and tcnt0. figure 11-7. phase correct pwm mode, timing diagram the timer/counter overflow flag (tov0) is set each time the counter reaches bottom. the interrupt flag can be used to generate an interrupt each time the counter reaches the bottom value. in phase correct pwm mode, the compare unit allows generation of pwm waveforms on the oc0x pins. setting the com0x1:0 bits to two will produce a non-inverted pwm. an inverted pwm output can be generated by setting the com0x1:0 to three: setting the com0a0 bits to tovn interrupt flag set ocnx interrupt flag set 1 2 3 tcntn period ocn ocn (comnx1:0 = 2) (comnx1:0 = 3) ocrnx update 80 8246b?avr?09/11 attiny2313a/4313 one allows the oc0a pin to toggle on compare ma tches if the wgm02 bit is set. this option is not available for the oc0b pin (see table 10-7 on page 66 ). the actual oc0x value will only be visible on the port pin if the data direction for th e port pin is set as output. the pwm waveform is generated by clearing (or setting) the oc0x register at the compare match between ocr0x and tcnt0 when the counter increments, and setti ng (or clearing) the oc0x register at com- pare match between ocr0x and tcnt0 when the counter decrements. the pwm frequency for the output when using phase correct pwm can be calculated by the following equation: the n variable represents the prescale factor (1, 8, 64, 256, or 1024). the extreme values for the ocr0a register represent special cases when generating a pwm waveform output in the phase correct pwm mode. if the ocr0a is set equal to bottom, the output will be continuously low an d if set equal to max the output will be continuously high for non-inverted pwm mode. for in verted pwm the output will have the opposite logic values. at the very start of period 2 in figure 11-7 on page 79 ocn has a transition from high to low even though there is no compare match. the poin t of this transition is to guarantee symmetry around bottom. there are two cases that give a transition without compare match. ? ocr0a changes its value from max, like in figure 11-7 on page 79 . when the ocr0a value is max the ocn pin value is the same as the result of a down-counting compare match. to ensure symmetry around bottom the ocn value at max must correspond to the result of an up-counting compare match. ? the timer starts counting from a value higher than the one in ocr0a, and for that reason misses the compare match and hence the ocn change that would have happened on the way up. 11.8 timer/counter timing diagrams the timer/counter is a synchronous design and the timer clock (clk t0 ) is therefore shown as a clock enable signal in the following figures. the figures include information on when interrupt flags are set. figure 11-8 contains timing data for basic timer/counter operation. the figure shows the count sequence close to the max val ue in all modes other than phase correct pwm mode. figure 11-8. timer/counter timing diagram, no prescaling figure 11-9 on page 81 shows the same timing data, but with the prescaler enabled. f ocnxpcpwm f clk_i/o n 510 ? ------------------ = clk tn (clk i/o /1) tovn clk i/o tcntn max - 1 max bottom bottom + 1 81 8246b?avr?09/11 attiny2313a/4313 figure 11-9. timer/counter timing dia gram, with prescaler (f clk_i/o /8) figure 11-10 shows the setting of ocf0b in all modes and ocf0a in all modes except ctc mode and pwm mode, where ocr0a is top. figure 11-10. timer/counter timing diagram, setting of ocf0x, with prescaler (f clk_i/o /8) figure 11-11 shows the setting of ocf0a and the clearing of tcnt0 in ctc mode and fast pwm mode where ocr0a is top. figure 11-11. timer/counter timing diagram, clear timer on compare match mode, with pres- caler (f clk_i/o /8) tovn tcntn max - 1 max bottom bottom + 1 clk i/o clk tn (clk i/o /8) ocfnx ocrnx tcntn ocrnx value ocrnx - 1 ocrnx ocrnx + 1 ocrnx + 2 clk i/o clk tn (clk i/o /8) ocfnx ocrnx tcntn (ctc) top top - 1 top bottom bottom + 1 clk i/o clk tn (clk i/o /8) 82 8246b?avr?09/11 attiny2313a/4313 11.9 register description 11.9.1 tccr0a ? timer/counter control register a ? bits 7:6 ? com0a1:0: compare match output a mode these bits control the output compare pin (oc0a) behavior. if one or both of the com0a1:0 bits are set, the oc0a output overrides the normal po rt functionality of the i/o pin it is connected to. however, note that the data direction r egister (ddr) bit corresponding to the oc0a pin must be set in order to enable the output driver. when oc0a is connected to the pin, the function of the com0a1:0 bits depends on the wgm02:0 bit setting. table 11-2 shows the com0a1:0 bit functionality when the wgm02:0 bits are set to a normal or ctc mode (non-pwm). table 11-3 shows the com0a1:0 bit functionality when the wgm01:0 bits are set to fast pwm mode. note: 1. a special case occurs when ocr0a equals top and com0a1 is set. in this case, the com- pare match is ignored, but the set or clear is done at top. see ?fast pwm mode? on page 77 for more details. bit 7 6 5 4 3 2 1 0 0x30 (0x50) com0a1 com0a0 com0b1 com0b0 ? ? wgm01 wgm00 tccr0a read/write r/w r/w r/w r/w r r r/w r/w initial value 0 0 0 0 0 0 0 0 table 11-2. compare output mode, non-pwm mode com0a1 com0a0 description 0 0 normal port operation, oc0a disconnected. 0 1 toggle oc0a on compare match 1 0 clear oc0a on compare match 1 1 set oc0a on compare match table 11-3. compare output mode, fast pwm mode (1) com0a1 com0a0 description 0 0 normal port operation, oc0a disconnected. 01 wgm02 = 0: normal port op eration, oc0a disconnected. wgm02 = 1: toggle oc0a on compare match. 1 0 clear oc0a on compare match, set oc0a at top 1 1 set oc0a on compare match, clear oc0a at top 83 8246b?avr?09/11 attiny2313a/4313 table 11-4 shows the com0a1:0 bit functionality when the wgm02:0 bits are set to phase cor- rect pwm mode. note: 1. a special case occurs when ocr0a equals top and com0a1 is set. in this case, the com- pare match is ignored, but the set or clear is done at top. see ?phase correct pwm mode? on page 79 for more details. ? bits 5:4 ? com0b1:0: compare match output b mode these bits control the output compare pin (oc0b) behavior. if one or both of the com0b1:0 bits are set, the oc0b output overrides the normal po rt functionality of the i/o pin it is connected to. however, note that the data direction r egister (ddr) bit corresponding to the oc0b pin must be set in order to enable the output driver. when oc0b is connected to the pin, the function of the com0b1:0 bits depends on the wgm02:0 bit setting. table 11-5 shows the com0b1:0 bit functionality when the wgm02:0 bits are set to a normal or ctc mode (non-pwm). table 11-6 shows the com0b1:0 bit functionality when the wgm02:0 bits are set to fast pwm mode. note: 1. a special case occurs when ocr0b equals top and com0b1 is set. in this case, the com- pare match is ignored, but the set or clear is done at top. see ?fast pwm mode? on page 77 for more details. table 11-4. compare output mode, phase correct pwm mode (1) com0a1 com0a0 description 0 0 normal port operation, oc0a disconnected. 01 wgm02 = 0: normal port op eration, oc0a disconnected. wgm02 = 1: toggle oc0a on compare match. 10 clear oc0a on compare match when up-counting. set oc0a on compare match when down-counting. 11 set oc0a on compare match when up-counting. clear oc0a on compare match when down-counting. table 11-5. compare output mode, non-pwm mode com0b1 com0b0 description 0 0 normal port operation, oc0b disconnected. 0 1 toggle oc0b on compare match 1 0 clear oc0b on compare match 1 1 set oc0b on compare match table 11-6. compare output mode, fast pwm mode (1) com0b1 com0b0 description 0 0 normal port operation, oc0b disconnected. 01reserved 1 0 clear oc0b on compare match, set oc0b at top 1 1 set oc0b on compare match, clear oc0b at top 84 8246b?avr?09/11 attiny2313a/4313 table 11-7 shows the com0b1:0 bit functionality when the wgm02:0 bits are set to phase cor- rect pwm mode. note: 1. a special case occurs when ocr0b equals top and com0b1 is set. in this case, the com- pare match is ignored, but the set or clear is done at top. see ?phase correct pwm mode? on page 79 for more details. ? bits 3, 2 ? res: reserved bits these bits are reserved bits in the atti ny2313a/4313 and will always read as zero. ? bits 1:0 ? wgm01:0: waveform generation mode combined with the wgm02 bit found in the tccr0b register, these bits control the counting sequence of the counter, the source for maximum (top) counter value, and what type of wave- form generation to be used, see table 11-8 . modes of operation supported by the timer/counter unit are: normal mode (counter), clear timer on compare match (ctc) mode, and two types of pulse width modulation (pwm) modes (see ?modes of operation? on page 76 ). notes: 1. max = 0xff 2. bottom = 0x00 table 11-7. compare output mode, phase correct pwm mode (1) com0b1 com0b0 description 0 0 normal port operation, ocr0b disconnected. 01reserved 10 clear orc0b on compare match when up-counting. set ocr0b on compare match when down-counting. 11 set ocr0b on compare match when up-counting. clear ocr0b on compare match when down-counting. table 11-8. waveform generation mode bit description mode wgm2 wgm1 wgm0 timer/count er mode of operation top update of ocrx at tov flag set on (1)(2) 0 0 0 0 normal 0xff immediate max 10 0 1 pwm, phase correct 0xff top bottom 2 0 1 0 ctc ocr0a immediate max 3 0 1 1 fast pwm 0xff top max 41 0 0reserved ? ? ? 51 0 1 pwm, phase correct ocr0a top bottom 61 1 0reserved ? ? ? 7 1 1 1 fast pwm ocr0a top top 85 8246b?avr?09/11 attiny2313a/4313 11.9.2 tccr0b ? timer/counter control register b ? bit 7 ? foc0a: force output compare a the foc0a bit is only active when the wgm bits specify a non-pwm mode. however, for ensuring compatibility with future devices, this bit must be set to zero when tccr0b is written when operating in pwm mode. when writing a logical one to the foc0a bit, an immediate compare match is forced on the waveform generation unit. the oc0a output is changed according to its com0a1:0 bits setting. note that the foc0a bit is implemented as a strobe. therefore it is the value present in the com0a1:0 bits that determines the effect of the forced compare. a foc0a strobe will not generate any interrupt, nor will it clear the timer in ctc mode using ocr0a as top. the foc0a bit is always read as zero. ? bit 6 ? foc0b: force output compare b the foc0b bit is only active when the wgm bits specify a non-pwm mode. however, for ensuring compatibility with future devices, this bit must be set to zero when tccr0b is written when operating in pwm mode. when writing a logical one to the foc0b bit, an immediate compare match is forced on the waveform generation unit. the oc0b output is changed according to its com0b1:0 bits setting. note that the foc0b bit is implemented as a strobe. therefore it is the value present in the com0b1:0 bits that determines the effect of the forced compare. a foc0b strobe will not generate any interrupt, nor will it clear the timer in ctc mode using ocr0b as top. the foc0b bit is always read as zero. ? bits 5:4 ? res: reserved bits these bits are reserved bits in the atti ny2313a/4313 and will always read as zero. ? bit 3 ? wgm02: waveform generation mode see the description in the ?tccr0a ? timer/counter control register a? on page 82 . ? bits 2:0 ? cs02:0: clock select the three clock select bits select the clock source to be used by the timer/counter. see table 11-9 on page 86 . bit 7 6 5 4 3 2 1 0 0x33 (0x53) foc0a foc0b ? ? wgm02 cs02 cs01 cs00 tccr0b read/write w w r r r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 86 8246b?avr?09/11 attiny2313a/4313 if external pin modes are used for the timer/counter0, transitions on the t0 pin will clock the counter even if the pin is configured as an output. this feature allows software control of the counting. 11.9.3 tcnt0 ? timer/counter register the timer/counter register gives direct ac cess, both for read and write operations, to the timer/counter unit 8-bit counter. writing to the tcnt0 register blocks (removes) the compare match on the following timer clock. modifying the counter (tcnt0) while the counter is running, introduces a risk of missing a compare match between tcnt0 and the ocr0x registers. 11.9.4 ocr0a ? output compare register a the output compare register a contains an 8-bi t value that is continuously compared with the counter value (tcnt0). a match can be used to generate an output compare interrupt, or to generate a waveform output on the oc0a pin. 11.9.5 ocr0b ? output compare register b the output compare register b contains an 8-bi t value that is continuously compared with the counter value (tcnt0). a match can be used to generate an output compare interrupt, or to generate a waveform output on the oc0b pin. table 11-9. clock select bit description cs02 cs01 cs00 description 0 0 0 no clock source (timer/counter stopped) 001clk i/o /(no prescaling) 010clk i/o /8 (from prescaler) 011clk i/o /64 (from prescaler) 100clk i/o /256 (from prescaler) 101clk i/o /1024 (from prescaler) 1 1 0 external clock source on t0 pin. clock on falling edge. 1 1 1 external clock source on t0 pin. clock on rising edge. bit 76543210 0x32 (0x52) tcnt0[7:0] tcnt0 read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 0x36 (0x56) ocr0a[7:0] ocr0a read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 0x3c (0x5c) ocr0b[7:0] ocr0b read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 87 8246b?avr?09/11 attiny2313a/4313 11.9.6 timsk ? timer/counter interrupt mask register ? bit 4 ? res: reserved bit this bit is reserved bit in the attiny 2313a/4313 and will alwa ys read as zero. ? bit 2 ? ocie0b: timer/counter0 output compare match b interrupt enable when the ocie0b bit is written to one, and the i-bit in the status register is set, the timer/counter compare match b interrupt is enab led. the corresponding interrupt is executed if a compare match in timer/counter occurs, i.e., when the ocf0b bit is set in the timer/counter interrupt flag register ? tifr. ? bit 1 ? toie0: timer/counter0 overflow interrupt enable when the toie0 bit is written to one, and the i-bit in the status register is set, the timer/counter0 overflow interrupt is enabled. the corresponding interrupt is executed if an overflow in timer/counter0 occurs, i.e., when the tov0 bit is set in the timer/counter 0 inter- rupt flag register ? tifr. ? bit 0 ? ocie0a: timer/counter0 output compare match a interrupt enable when the ocie0a bit is written to one, and th e i-bit in the status register is set, the timer/counter0 compare match a interrupt is enabled. the corresponding interrupt is executed if a compare match in timer/counter0 occurs, i.e., when the ocf0a bit is set in the timer/counter 0 interrupt flag register ? tifr. 11.9.7 tifr ? timer/counter interrupt flag register ? bit 4 ? res: reserved bit this bit is reserved bit in the attiny 2313a/4313 and will alwa ys read as zero. ? bit 2 ? ocf0b: output compare flag 0 b the ocf0b bit is set when a compare match occurs between the timer/counter and the data in ocr0b ? output compare register0 b. ocf0b is cleared by hardware when executing the cor- responding interrupt handling vector. alternatively, ocf0b is cleared by writing a logic one to the flag. when the i-bit in sreg, ocie0b (timer/counter compare b match interrupt enable), and ocf0b are set, the timer/counter compare match interrupt is executed. ? bit 1 ? tov0: timer/counter0 overflow flag the bit tov0 is set when an overflow occurs in timer/counter0. tov0 is cleared by hardware when executing the corresponding interrupt handling vector. alternatively, tov0 is cleared by writing a logic one to the flag. when the sreg i-bit, toie0 (timer/counter0 overflow interrupt enable), and tov0 are set, the timer/counter0 overflow interrupt is executed. bit 76543210 0x39 (0x59) toie1 ocie1a ocie1b ? icie1 ocie0b toie0 ocie0a timsk read/write r/w r/w r/w r r/w r/w r/w r/w initial value00000000 bit 76543210 0x38 (0x58) tov1 ocf1a ocf1b ? icf1 ocf0b tov0 ocf0a tifr read/write r/w r/w r/w r r/w r/w r/w r/w initial value00000000 88 8246b?avr?09/11 attiny2313a/4313 the setting of this flag is dependent of the wgm02:0 bit setting. refer to table 11-8 , ?waveform generation mode bit description? on page 84 . ? bit 0 ? ocf0a: output compare flag 0 a the ocf0a bit is set when a compare match occurs between the timer/counter0 and the data in ocr0a ? output compare register0 a. ocf0a is cleared by hardware when executing the corresponding interrupt handling vector. alternatively, ocf0a is cleared by writing a logic one to the flag. when the i-bit in sreg, ocie0a (timer/counter0 compare match interrupt enable), and ocf0a are set, the timer/counter0 compare match interrupt is executed. 89 8246b?avr?09/11 attiny2313a/4313 12. 16-bit timer/counter1 12.1 features ? true 16-bit design (i.e., allows 16-bit pwm) ? two independent output compare units ? double buffered outp ut compare registers ? one input capture unit ? input capture noise canceler ? clear timer on compare match (auto reload) ? glitch-free, phase correct pu lse width modulator (pwm) ? variable pwm period ? frequency generator ? external event counter ? four independent interrupt sources (tov1, ocf1a, ocf1b, and icf1) 12.2 overview the 16-bit timer/counter unit allows accurate program execution timing (event management), wave generation, and signal timing measurement. a simplified block diagram of the 16-bit timer/counter is shown in figure 12-1 . for the actual placement of i/o pins, refer to ?pinout attiny2313a/4313? on page 2 . cpu accessible i/o regis- ters, including i/o bits and i/o pins, are shown in bold. the device-specific i/o register and bit locations are listed in the ?register description? on page 111 . figure 12-1. 16-bit timer/counter block diagram (note:) note: refer to figure 1-1 on page 2 for timer/counter1 pin placement and description. clock select timer/counter data b u s ocrna ocrnb icrn = = tcntn waveform generation waveform generation ocna ocnb noise canceler icpn = fixed top values edge detector control logic = 0 top bottom count clear direction tovn (int.req.) ocna (int.req.) ocnb (int.req.) icfn (int.req.) tccrna tccrnb ( from analog comparator ouput ) tn edge detector ( from prescaler ) clk tn 90 8246b?avr?09/11 attiny2313a/4313 most register and bit references in this sect ion are written in general form. a lower case ?n? replaces the timer/counter number, and a lower case ?x? replaces the output compare unit channel. however, when using the register or bit defines in a program, the precise form must be used, i.e., tcnt1 for accessing timer/counter1 counter value and so on. 12.2.1 registers the timer/counter (tcnt1), output compare registers (ocr1a/b), and input capture regis- ter (icr1) are all 16-bit registers. special procedures must be followed when accessing the 16- bit registers. these procedures are described in the section ?accessing 16-bit registers? on page 107 . the timer/counter co ntrol registers (tccr1a/b) are 8-bit registers and have no cpu access restrictions. interrupt requests (abbrevi ated to int.req. in the figure) signals are all visible in the timer interrupt flag register (tifr). all interrupts are in dividually masked with the timer interrupt mask register (timsk). tifr and timsk are not shown in the figure. the timer/counter can be clocked internally, via the prescaler, or by an external clock source on the t1 pin. the clock select logic block controls which clock source and edge the timer/counter uses to increment (or decrement) its value. the timer/counter is inactive when no clock source is selected. the output from the clock select logic is referred to as the timer clock (clk t 1 ). the double buffered output compare registers (ocr1a/b) are compared with the timer/coun- ter value at all time. the result of the compare can be used by the waveform generator to generate a pwm or variable frequency output on the output compare pin (oc1a/b). see ?out- put compare units? on page 94. . the compare match event will also set the compare match flag (ocf1a/b) which can be used to generate an output compare interrupt request. the input capture register can capture the timer/ counter value at a given external (edge trig- gered) event on either the input capture pin (icp1) or on the analog comparator pins ( see ?analog comparator? on page 168. ) the input capture unit includes a digital filtering unit (noise canceler) for reducing the chance of capturing noise spikes. the top value, or maximum timer/counter value, can in some modes of operation be defined by either the ocr1a register, the icr1 regist er, or by a set of fixed values. when using ocr1a as top value in a pwm mode, the ocr1a register can not be used for generating a pwm output. however, the top value will in this case be do uble buffered allowing the top value to be changed in run time. if a fixed top value is required, the icr1 register can be used as an alternative, freeing the ocr1a to be used as pwm output. 12.2.2 definitions the following definitions are used extensively throughout the section: table 12-1. definitions constant description bottom the counter reaches bottom when it becomes 0x0000 max the counter reaches its maximum when it becomes 0xffff (decimal 65535) top the counter reaches the top when it become s equal to the highest value in the count sequence. the top value can be assigned to be one of the fixed values: 0x00ff, 0x01ff, or 0x03ff, or to the value stored in the ocr1a or icr1 register. the assignment depends on the mode of operation 91 8246b?avr?09/11 attiny2313a/4313 12.2.3 compatibility the 16-bit timer/counter has been updated and impr oved from previous versions of the 16-bit avr timer/counter. this 16-bit timer/counter is fully compatible with the earlier version regarding: ? all 16-bit timer/counter related i/o register address locations, including timer interrupt registers. ? bit locations inside all 16-bit timer/counter registers, including timer interrupt registers. ? interrupt vectors. the following control bits have changed name, but have same functionality and register location: ? pwm10 is changed to wgm10. ? pwm11 is changed to wgm11. ? ctc1 is changed to wgm12. the following bits are added to the 16-bit timer/counter control registers: ? foc1a and foc1b are added to tccr1a. ? wgm13 is added to tccr1b. the 16-bit timer/counter has improvements that will affect the compatibility in some special cases. 12.3 timer/counter clock sources the timer/counter can be clocked by an internal or an external clock source. the clock source is selected by the clock select logic which is controlled by the clock select (cs12:0) bits located in the timer/counter control register b (tccr1b). for details on clock sources and prescaler, see ?timer/counter0 and timer/counter1 prescalers? on page 118 . 12.4 counter unit the main part of the 16-bit timer/counter is th e programmable 16-bit bi-directional counter unit. figure 12-2 shows a block diagram of the counter and its surroundings. figure 12-2. counter unit block diagram signal description (internal signals): count increment or decrement tcnt1 by 1. direction select between increment and decrement. clear clear tcnt1 (set all bits to zero). temp (8-bit) data bus (8-bit) tcntn (16-bit counter) tcntnh (8-bit) tcntnl (8-bit) control logic count clear direction tovn (int.req.) clock select top bottom tn edge detector ( from prescaler ) clk tn 92 8246b?avr?09/11 attiny2313a/4313 clk t 1 timer/counter clock. top signalize that tcnt1 has reached maximum value. bottom signalize that tcnt1 has re ached minimum value (zero). the 16-bit counter is mapped into two 8-bit i/o memory locations: counter high (tcnt1h) con- taining the upper eight bits of the counter, and counter low (tcnt1l) containing the lower eight bits. the tcnt1h register can only be indirect ly accessed by the cpu. when the cpu does an access to the tcnt1h i/o location, the cpu accesses the high byte temporary register (temp). the temporary register is updated with the tcnt1h value when the tcnt1l is read, and tcnt1h is updated with the temporary register va lue when tcnt1l is written. this allows the cpu to read or write the entire 16-bit counter value within one clock cycle via the 8-bit data bus. it is important to notice that there are special cases of writing to the tcnt1 register when the counter is counting that will gi ve unpredictable results. the s pecial cases are described in the sections where they are of importance. depending on the mode of operation used, the counter is cleared, incremented, or decremented at each timer clock (clk t 1 ). the clk t 1 can be generated from an external or internal clock source, selected by the clock select bits (cs12:0). when no clock source is selected (cs12:0 = 0) the timer is stopped. however, the tcnt1 value can be accessed by the cpu, independent of whether clk t 1 is present or not. a cpu write overrides (has priority over) all counter clear or count operations. the counting sequence is determined by the setting of the waveform generation mode bits (wgm13:0) located in the timer/counter control registers a and b (tccr1a and tccr1b). there are close connections between how the counter behaves (counts) and how waveforms are generated on the output compare outputs oc1x. for more details about advanced counting sequences and waveform generation, see ?modes of operation? on page 97 . the timer/counter overflow flag (tov1) is set according to the mode of operation selected by the wgm13:0 bits. tov1 can be used for generating a cpu interrupt. 12.5 input capture unit the timer/counter incorporates an input capture unit that can capture external events and give them a time-stamp indicating time of occurrence. the external signal indicating an event, or mul- tiple events, can be applied via the icp1 pin or al ternatively, via the analog-comparator unit. the time-stamps can then be used to calculate frequenc y, duty-cycle, and other features of the sig- nal applied. alternatively the time-stamps can be used for creating a log of the events. the input capture unit is illustrated by the block diagram shown in figure 12-3 . the elements of the block diagram that are not directly a part of the input capture unit are gray shaded. the small ?n? in register and bit names indicates the timer/counter number. 93 8246b?avr?09/11 attiny2313a/4313 figure 12-3. input capture unit block diagram when a change of the logic level (an event) occurs on the input capture pin (icp1), alternatively on the analog comparator output (aco), and this change confirms to the setting of the edge detector, a capture will be triggered. when a captur e is triggered, the 16-bit value of the counter (tcnt1) is written to the input capture register (icr1). the input capture flag (icf1) is set at the same system clock as the tcnt1 value is copi ed into icr1 register. if enabled (icie1 = 1), the input capture flag generates an input capt ure interrupt. the icf1 flag is automatically cleared when the interrupt is executed. alternativ ely the icf1 flag can be cleared by software by writing a logical one to its i/o bit location. reading the 16-bit value in the input capture register (icr1) is done by first reading the low byte (icr1l) and then the high byte (icr1h). when the low byte is read the high byte is copied into the high byte temporary regi ster (temp). when the cpu reads the icr1h i/o location it will access the temp register. the icr1 register can only be written when us ing a waveform generation mode that utilizes the icr1 register for defining the counter?s top value. in these cases the waveform genera- tion mode (wgm13:0) bits must be set before the top value can be written to the icr1 register. when writing the icr1 re gister the high byte must be written to the icr1h i/o location before the low byte is written to icr1l. for more information on how to access the 16-bit registers refer to ?accessing 16-bit registers? on page 107 . 12.5.1 input capture trigger source the main trigger source for the input capture unit is the input capture pin (icp1). timer/counter1 can alternatively use the analog comparator output as trigger source for the input capture unit. the analog comparator is selected as trigger source by setting the analog comparator input capture (acic) bit in the analog comparator control and status register (acsr). be aware that changing trigger source can trigger a capture. the input capture flag must therefore be cleared after the change. icfn (int.req.) analog comparator write icrn (16-bit register) icrnh (8-bit) noise canceler icpn edge detector temp (8-bit) data bus (8-bit) icrnl (8-bit) tcntn (16-bit counter) tcntnh (8-bit) tcntnl (8-bit) acic* icnc ices aco* 94 8246b?avr?09/11 attiny2313a/4313 both the input capture pin (icp1) and the analog comparator output (aco) inputs are sampled using the same technique as for the t1 pin ( figure 13-1 on page 118 ). the edge detector is also identical. however, when the noise canceler is enabled, additional logic is inserted before the edge detector, which increases t he delay by four system clock cycles. note that the input of the noise canceler and edge detector is always enabl ed unless the timer/counter is set in a wave- form generation mode that uses icr1 to define top. an input capture can be trigger ed by software by controlling the port of the icp1 pin. 12.5.2 noise canceler the noise canceler improves noise immunity by using a simple digital filtering scheme. the noise canceler input is monitored over four samples, and all four must be equal for changing the output that in turn is used by the edge detector. the noise canceler is enabled by setting the input capture noise canceler (icnc1) bit in timer/counter control register b (tccr1b). when enabled the noise canceler introduces addi- tional four system clock cycles of delay from a change applied to the input, to the update of the icr1 register. the noise canceler uses the sy stem clock and is therefore not affected by the prescaler. 12.5.3 using the input capture unit the main challenge when using the input capture unit is to assign enough processor capacity for handling the incoming events. the time between two events is critical. if the processor has not read the captured value in th e icr1 register before the nex t event occurs, the icr1 will be overwritten with a new value. in this case the result of the ca pture will be incorrect. when using the input capture interrupt, the icr1 register should be read as early in the inter- rupt handler routine as possible. even though the input capture interrupt has relatively high priority, the maximum interrupt response time is dependent on the maximum number of clock cycles it takes to handle any of the other interrupt requests. using the input capture unit in any mode of operation when the top value (resolution) is actively changed during operation, is not recommended. measurement of an external signal?s duty cycle requires that the trigger edge is changed after each capture. changing the edge sensing must be done as early as possible after the icr1 register has been read. after a change of the edge, the input capture flag (icf1) must be cleared by software (writing a logical one to the i/o bit location). for measuring frequency only, the clearing of the icf1 flag is not required (if an interrupt handler is used). 12.6 output compare units the 16-bit comparator continuously compares tcnt1 with the output compare register (ocr1x). if tcnt equals ocr1x the comparator signals a match. a match will set the output compare flag (ocf1x) at the next timer clock cycle. if enabled (ocie1x = 1), the output com- pare flag generates an output compare interrupt. the ocf1x flag is automatically cleared when the interrupt is executed. alternatively the ocf1x flag can be cleare d by software by writ- ing a logical one to its i/o bit location. the waveform generator uses the match signal to generate an output according to operating mode set by the waveform generation mode (wgm13:0) bits and compare output mode (com1x1:0) bits. the top and bottom signals are used by the waveform generator for handling the special cases of the extreme values in some modes of operation ( see ?modes of operation? on page 97. ) 95 8246b?avr?09/11 attiny2313a/4313 a special feature of output compare unit a allows it to define the timer/counter top value (i.e., counter resolution). in addition to the counter resolution, the top value defines the period time for waveforms generated by the waveform generator. figure 12-4 shows a block diagram of the output compare unit. the small ?n? in the register and bit names indicates the device number (n = 1 for timer/counter 1), and the ?x? indicates output compare unit (a/b). the elements of the block diagram that are not directly a part of the output compare unit are gray shaded. figure 12-4. output compare unit, block diagram the ocr1x register is double buffered when using any of the twelve pulse width modulation (pwm) modes. for the normal and clear timer on compare (ctc) modes of operation, the double buffering is disabled. the double buffering synchronizes the update of the ocr1x com- pare register to either top or bottom of the counting sequence. the synchronization prevents the occurrence of odd-length, non-symmetrical pwm pulses, thereby making the out- put glitch-free. the ocr1x register access may seem complex, but this is not case. when the double buffering is enabled, the cpu has access to the ocr1x buffer register, and if double buffering is dis- abled the cpu will access the ocr1x directly. the content of the ocr1x (buffer or compare) register is only changed by a write operation (the timer/counter does not update this register automatically as the tcnt1 and icr1 register). therefore ocr1x is not read via the high byte temporary register (temp). however, it is a good practice to read the low byte first as when accessing other 16-bit registers. writing the ocr1x registers must be done via the temp reg- ister since the compare of all 16 bits is done continuously. the high byte (ocr1xh) has to be written first. when the high byte i/o location is written by the cpu, the temp register will be updated by the value written. then when the low by te (ocr1xl) is written to the lower eight bits, the high byte will be copied into the upper 8-bits of either the ocr1x bu ffer or ocr1x compare register in the same system clock cycle. ocfnx (int.req.) = (16-bit comparator ) ocrnx buffer (16-bit register) ocrnxh buf. (8-bit) ocnx temp (8-bit) data bus (8-bit) ocrnxl buf. (8-bit) tcntn (16-bit counter) tcntnh (8-bit) tcntnl (8-bit) comnx1:0 wgmn3:0 ocrnx (16-bit register) ocrnxh (8-bit) ocrnxl (8-bit) waveform generator top bottom 96 8246b?avr?09/11 attiny2313a/4313 for more information of how to access the 16-bit registers refer to ?accessing 16-bit registers? on page 107 . 12.6.1 force output compare in non-pwm waveform generation modes, the match output of the comparator can be forced by writing a one to the force output compare (foc1x) bit. forcing compare match will not set the ocf1x flag or reload/clear the timer, but the oc1x pin will be updated as if a real compare match had occurred (the com11:0 bits settings define whether the oc1x pin is set, cleared or toggled). 12.6.2 compare match bloc king by tcnt1 write all cpu writes to the tcnt1 register will block any compare match that o ccurs in the next timer clock cycle, even when the timer is stopped. this feature allows ocr1x to be initialized to the same value as tcnt1 without triggering an inte rrupt when the timer/counter clock is enabled. 12.6.3 using the output compare unit since writing tcnt1 in any mode of operation will block all comp are matches for one timer clock cycle, there are risks involved when changing tcnt1 when using any of the output compare channels, independent of whether the timer/counter is running or not. if the value written to tcnt1 equals the ocr1x value, the compare matc h will be missed, resulting in incorrect wave- form generation. do not write the tcnt1 equal to top in pwm modes with variable top values. the compare match for the top will be ignored and the counte r will continue to 0xffff. similarly, do not write the tcnt1 value equal to bottom when the counter is downcounting. the setup of the oc1x should be performed before setting the data direction register for the port pin to output. the easiest way of setting the oc1x value is to use the force output com- pare (foc1x) strobe bits in normal mode. the oc1x register keeps its value even when changing between waveform generation modes. be aware that the com1x1:0 bits are not doubl e buffered together with the compare value. changing the com1x1:0 bits will take effect immediately. 12.7 compare match output unit the compare output mode (com1x1:0) bits have two functions. the waveform generator uses the com1x1:0 bits for defining the output compare (oc1x) state at the next compare match. secondly the com1x1:0 bits control the oc1x pin output source. figure 12-5 shows a simplified schematic of the logic affected by the com1x1:0 bit setting. the i/o registers, i/o bits, and i/o pins in the figure are shown in bold. only the parts of the general i/o port control registers (ddr and port) that are affected by the com1x1:0 bits are shown. when referring to the oc1x state, the reference is for the internal oc1x register, not the oc1x pin. if a system reset occur, the oc1x register is reset to ?0?. 97 8246b?avr?09/11 attiny2313a/4313 figure 12-5. compare match output unit, schematic the general i/o port function is overridden by the output compare (oc1x) from the waveform generator if either of the com1x1:0 bits are set. however, the oc1x pin direction (input or out- put) is still controlled by the data direction register (ddr) for the port pin. the data direction register bit for the oc1x pin (ddr_oc1x) must be set as output before the oc1x value is visi- ble on the pin. the port override function is generally independent of the waveform generation mode, but there are some exceptions. refer to table 12-2 , table 12-3 and table 12-4 for details. the design of the output compare pin logic allows initialization of the oc1x state before the out- put is enabled. note that some com1x1:0 bi t settings are reserved for certain modes of operation. see ?register description? on page 111. the com1x1:0 bits have no effect on the input capture unit. 12.7.1 compare output mode and waveform generation the waveform generator uses the com1x1:0 bits differently in normal, ctc, and pwm modes. for all modes, setting the com1x1:0 = 0 tells the waveform generator that no action on the oc1x register is to be performed on the next compare match. for compare output actions in the non-pwm modes refer to table 12-2 on page 111 . for fast pwm mode refer to table 12-3 on page 111 , and for phase correct and phase and frequency correct pwm refer to table 12-4 on page 112 . a change of the com1x1:0 bits st ate will have effect at the first compare matc h after the bits are written. for non-pwm modes, the action can be fo rced to have immediate effect by using the foc1x strobe bits. 12.8 modes of operation the mode of operation, i.e., the behavior of the timer/counter and the output compare pins, is defined by the combination of the waveform generation mode (wgm13:0) and compare output port ddr dq dq ocnx pin ocnx dq waveform generator comnx1 comnx0 0 1 data b u s focnx clk i/o 98 8246b?avr?09/11 attiny2313a/4313 mode (com1x1:0) bits. the compare output mode bits do not affect the counting sequence, while the waveform generation mode bits do. the com1x1:0 bits control whether the pwm out- put generated should be inverted or not (inverted or non-inverted pwm). for non-pwm modes the com1x1:0 bits control whether the output should be set, cleared or toggle at a compare match ( see ?compare match output unit? on page 96. ) for detailed timing information refer to ?timer/counter timing diagrams? on page 105 . 12.8.1 normal mode the simplest mode of operation is the normal mode (wgm13:0 = 0). in this mode the counting direction is always up (incrementing), and no counter clear is performed. the counter simply overruns when it passes its maximum 16-bit value (max = 0xffff) and then restarts from the bottom (0x0000). in normal operation the timer/counter overflow flag (tov1) will be set in the same timer clock cycle as the tcnt1 beco mes zero. the tov1 flag in this case behaves like a 17th bit, except that it is only set, not cleared. however, combined with the timer overflow interrupt that automatically clears the tov1 flag, the timer resolution can be increased by soft- ware. there are no special cases to consider in the normal mode, a new counter value can be written anytime. the input capture unit is easy to use in normal mode. however, observe that the maximum interval between the external events must not exceed the resolution of the counter. if the interval between events are too long, the timer overflow interrupt or the prescaler must be used to extend the resolution for the capture unit. the output compare units can be used to generat e interrupts at some given time. using the output compare to gene rate waveforms in norm al mode is not recommended, since this will occupy too much of the cpu time. 12.8.2 clear timer on compare match (ctc) mode in clear timer on compare or ctc mode (wgm13:0 = 4 or 12), the ocr1a or icr1 register are used to manipulate the counter resolution. in ctc mode the counter is cleared to zero when the counter value (tcnt1) matches either the ocr1a (wgm13:0 = 4) or the icr1 (wgm13:0 = 12). the ocr1a or icr1 define the top value for the counter, hence also its resolution. this mode allows greater control of the compare match output frequency. it also simplifies the opera- tion of counting external events. the timing diagram for the ctc mode is shown in figure 12-6 . the counter value (tcnt1) increases until a compare match occurs with either ocr1a or icr1, and then counter (tcnt1) is cleared. 99 8246b?avr?09/11 attiny2313a/4313 figure 12-6. ctc mode, timing diagram an interrupt can be generated at each time the counter value reaches the top value by either using the ocf1a or icf1 flag according to the register used to define the top value. if the inter- rupt is enabled, the interrupt handler routine can be used for updating the top value. however, changing the top to a value close to bottom w hen the counter is running with none or a low prescaler value must be done with care since the ctc mode does not have the double buffering feature. if the new value written to ocr1a or icr1 is lower than the current value of tcnt1, the counter will miss the compare matc h. the counter will th en have to count to its maximum value (0xffff) and wrap around starting at 0x0000 before the compare match can occur. in many cases this feature is not desirable. an alternative will then be to use the fast pwm mode using ocr1a for defining top (wgm13:0 = 15) si nce the ocr1a then will be double buffered. for generating a waveform output in ctc mode, the ocfa output can be set to toggle its logical level on each compare match by setting the compare output mode bits to toggle mode (com1a1:0 = 1). the ocf1a value will not be visi ble on the port pin unless the data direction for the pin is set to output (ddr_ocf1a = 1). the waveform generated will have a maximum frequency of f oc 1 a = f clk_i/o /2 when ocr1a is set to zero (0x0000). the waveform frequency is defined by the following equation: the n variable represents the prescaler factor (1, 8, 64, 256, or 1024). as for the normal mode of operation, the tov1 flag is set in the same timer clock cycle that the counter counts from max to 0x0000. 12.8.3 fast pwm mode the fast pulse width modulation or fast pwm mode (wgm13:0 = 5, 6, 7, 14, or 15) provides a high frequency pwm waveform generation option. the fast pwm differs from the other pwm options by its single-slope operation. the counter counts from bottom to top then restarts from bottom. in non-inverting compare output mode, the output compare (oc1x) is set on the compare match between tcnt1 and ocr1x, and cleared at top. in inverting compare output mode output is cleared on compare match and set at top. due to the single-slope oper- ation, the operating frequency of the fast pwm mode can be twice as high as the phase correct and phase and frequency correct pwm modes that use dual-slope operation. this high fre- quency makes the fast pwm mode well suited for power regulation, rectification, and dac applications. high frequency allows physically sm all sized external com ponents (coils, capaci- tors), hence reduces total system cost. tcntn ocna (toggle) ocna interrupt flag set or icfn interrupt flag set (interrupt on top) 1 4 period 2 3 (comna1:0 = 1) f ocna f clk_i/o 2 n 1 ocrna + () ?? --------------------------------------------------- = 100 8246b?avr?09/11 attiny2313a/4313 the pwm resolution for fast pwm can be fixed to 8-, 9-, or 10-bit, or defined by either icr1 or ocr1a. the minimum resolution allowed is 2-bit (icr1 or ocr1a set to 0x0003), and the max- imum resolution is 16-bit (icr1 or ocr1a set to max). the pwm resolution in bits can be calculated by using the following equation: in fast pwm mode the counter is incremented until the counter value matches either one of the fixed values 0x00ff, 0x01ff, or 0x03ff (wgm13:0 = 5, 6, or 7), the value in icr1 (wgm13:0 = 14), or the value in ocr1a (wgm13:0 = 15). the counter is then cleared at the following timer clock cycle. the timing diagram for the fast pwm mode is shown in figure 12-7 . the figure shows fast pwm mode when ocr1a or icr1 is us ed to define top. the tcnt1 value is in the timing diagram shown as a histogram for illu strating the single-slope operation. the diagram includes non-inverted and inverted pwm outputs. the small horizontal line marks on the tcnt1 slopes represent compare matc hes between ocr1x and tcnt1. the oc1x interrupt flag will be set when a compare match occurs. figure 12-7. fast pwm mode, timing diagram the timer/counter overflow flag (tov1) is set each time the counter reaches top. in addition the ocf1a or icf1 flag is set at the same timer clock cycle as tov1 is set when either ocr1a or icr1 is used for defining the top value. if one of the interrupts are enabled, the interrupt han- dler routine can be used for updating the top and compare values. when changing the top value the program must ensure that the new top value is higher or equal to the value of all of the compare registers. if the top value is lower than any of the compare registers, a compare match will never occur between the tcnt1 and the ocr1x. note that when using fixed top values the unused bits are masked to zero when any of the ocr1x registers are written. the procedure for updating icr1 differs from updating ocr1a when used for defining the top value. the icr1 register is not double buffered. this means that if icr1 is changed to a low value when the counter is running with none or a low prescaler value, there is a risk that the new icr1 value written is lower than the current va lue of tcnt1. the result will then be that the counter will miss the compare matc h at the top value. the counter will then have to count to the max value (0xffff) and wrap around starting at 0x0000 before the compare match can occur. r fpwm top 1 + () log 2 () log ---------------------------------- - = tcntn ocrnx/top update and tovn interrupt flag set and ocna interrupt flag set or icfn interrupt flag set (interrupt on top) 1 7 period 2 3 4 5 6 8 ocnx ocnx (comnx1:0 = 2) (comnx1:0 = 3) 101 8246b?avr?09/11 attiny2313a/4313 the ocr1a register however, is double buffered. this feature allows the ocr1a i/o location to be written anytime. when the ocr1a i/o location is written the value written will be put into the ocr1a buffer register. th e ocr1a compare register will th en be updated with the value in the buffer register at the next timer clo ck cycle the tcnt1 matches top. the update is done at the same timer clock cycle as the tcnt1 is cleared and the tov1 flag is set. using the icr1 register for defining top work s well when using fixed top values. by using icr1, the ocr1a register is free to be used for generating a pwm output on oc1a. however, if the base pwm frequency is actively change d (by changing the top value), using the ocr1a as top is clearly a better choice due to its double buffer feature. in fast pwm mode, the compare units allow generation of pwm waveforms on the oc1x pins. setting the com1x1:0 bits to two will produce a non-inverted pwm and an inverted pwm output can be generated by setting the com1x1:0 to three (see table 12-2 on page 111 ). the actual oc1x value will only be visible on the port pin if th e data direction for the po rt pin is set as output (ddr_oc1x). the pwm waveform is generated by setting (or clearing) the oc1x register at the compare match between ocr1x and tcnt1, and clearing (or setting) the oc1x register at the timer clock cycle the counter is cleared (changes from top to bottom). the pwm frequency for the output can be calculated by the following equation: the n variable represents the prescaler divider (1, 8, 64, 256, or 1024). the extreme values for the ocr1x register represents special cases when generating a pwm waveform output in the fast pwm mode. if the ocr1x is set equal to bottom (0x0000) the out- put will be a narrow spike for eac h top+1 timer clock cycle. se tting the ocr1x equal to top will result in a const ant high or low output (depending on the polarity of the output set by the com1x1:0 bits.) a frequency (with 50% duty cycle) waveform output in fast pwm mode can be achieved by set- ting ocf1a to toggle its logical level on each compare match (com1a1:0 = 1). the waveform generated will have a maximum frequency of f oc 1 a = f clk_i/o /2 when ocr1a is set to zero (0x0000). this feature is similar to the ocf1a toggle in ctc mode, except the double buffer feature of the output compare unit is enabled in the fast pwm mode. 12.8.4 phase correct pwm mode the phase correct pulse width modulation or phase correct pwm mode (wgm13:0 = 1, 2, 3, 10, or 11) provides a high resolution phase correct pwm waveform generation option. the phase correct pwm mode is, like the phase and frequency correct pwm mode, based on a dual- slope operation. the counter counts repeatedly from bottom (0x0000) to top and then from top to bottom. in non-inverting compare output mode, the output compare (oc1x) is cleared on the compare match between tcnt1 and ocr1x while upcounting, and set on the compare match while downcounting. in inverting output compare mode, the operation is inverted. the dual-slope operation has lower maximum operation frequency than single slope operation. however, due to the symmetric feat ure of the dual-slope pwm modes, these modes are preferred for motor control applications. the pwm resolution for the phase correct pwm mode can be fixed to 8-, 9-, or 10-bit, or defined by either icr1 or ocr1a. the minimum resolution allowed is 2-bit (icr1 or ocr1a set to f ocnxpwm f clk_i/o n 1 top + () ? ---------------------------------- - = 102 8246b?avr?09/11 attiny2313a/4313 0x0003), and the maximum resolution is 16-bit (icr1 or ocr1a set to max). the pwm resolu- tion in bits can be calculated by using the following equation: in phase correct pwm mode the counter is incremented until the counter value matches either one of the fixed values 0x00ff, 0x01ff, or 0x03ff (wgm13:0 = 1, 2, or 3), the value in icr1 (wgm13:0 = 10), or the value in ocr1a (wgm13:0 = 11). the counter has then reached the top and changes the count direct ion. the tcnt1 value will be equa l to top for one timer clock cycle. the timing diagram for the phase correct pwm mode is shown on figure 12-8 on page 102 . the figure shows phase correct pwm mode w hen ocr1a or icr1 is used to define top. the tcnt1 value is in the timing diagram shown as a histogram for illustrating the dual-slope operation. the diagram includes non-inverted and inverted pwm outputs. the small horizontal line marks on the tcnt1 slopes represent compare matches between ocr1x and tcnt1. the oc1x interrupt flag will be set when a compare match occurs. figure 12-8. phase correct pwm mode, timing diagram the timer/counter overflow flag (tov1) is set each time the counter reaches bottom. when either ocr1a or icr1 is used for defining the top value, the ocf1a or icf1 flag is set accord- ingly at the same timer clock cycle as the ocr1x registers are updated with the double buffer value (at top). the interrupt flags can be used to generate an interrupt each time the counter reaches the top or bottom value. when changing the top value the program must ensure that the new top value is higher or equal to the value of all of the compare registers. if the top value is lower than any of the compare registers, a compare match will never occur between the tcnt1 and the ocr1x. note that when using fixed top values, the unus ed bits are masked to zero when any of the ocr1x registers are written. as the third period shown in figure 12-8 illustrates, changing the top actively while the timer/counter is running in the phase correct mode can result in an unsymmetrical output. the reason for this can be found in the time of update of the ocr1x reg- ister. since the ocr1x update occurs at top, the pwm period starts and ends at top. this r pcpwm top 1 + () log 2 () log ---------------------------------- - = ocrnx/top update and ocna interrupt flag set or icfn interrupt flag set (interrupt on top) 1 2 3 4 tovn interrupt flag set (interrupt on bottom) tcntn period ocnx ocnx (comnx1:0 = 2) (comnx1:0 = 3) 103 8246b?avr?09/11 attiny2313a/4313 implies that the length of the falling slope is determined by the previous top value, while the length of the rising slope is determined by th e new top value. when these two values differ the two slopes of the period will differ in length. the difference in length gives the unsymmetrical result on the output. it is recommended to use the phase and frequency correct mode instead of the phase correct mode when changing the top value while the timer/counter is running. when using a static top value there are practically no differences between the two modes of operation. in phase correct pwm mode, the compare units allow generation of pwm waveforms on the oc1x pins. setting the com1x1:0 bits to tw o will produce a non-inverte d pwm and an inverted pwm output can be generated by setting the com1x1:0 to three (see table 12-3 on page 111 ). the actual oc1x value will only be visible on the port pin if the data direction for the port pin is set as output (ddr_oc1x). the pwm waveform is gene rated by setting (or clearing) the oc1x register at the compare match between ocr1x and tcnt1 when the counter increments, and clearing (or setting) the oc1x register at compare match between ocr1x and tcnt1 when the counter decrements. the pwm frequency for the output when using phase correct pwm can be calculated by the following equation: the n variable represents the prescaler divider (1, 8, 64, 256, or 1024). the extreme values for the ocr1x register represent special cases when generating a pwm waveform output in the phase correct pwm mode. if the ocr1x is set equal to bottom the output will be continuously low and if set equal to top the output will be continuously high for non-inverted pwm mode. for in verted pwm the output will have the opposite logic values. 12.8.5 phase and frequency correct pwm mode the phase and frequency correct pulse width modulation, or phase and frequency correct pwm mode (wgm13:0 = 8 or 9) provides a high reso lution phase and frequency correct pwm wave- form generation option. the phase and frequency correct pwm mode is, like the phase correct pwm mode, based on a dual-slope operation. the counter counts repeatedly from bottom (0x0000) to top and then from top to bottom. in non-inverting compare output mode, the output compare (oc1x) is cleared on the compare match between tcnt1 and ocr1x while upcounting, and set on the compare match while downcounting. in inverting compare output mode, the operation is inverted. the dual-slope operation gives a lower maximum operation fre- quency compared to the single-slope operation. howe ver, due to the symmetric feature of the dual-slope pwm modes, these modes are preferred for motor control applications. the main difference between the phase correct, and the phase and frequency correct pwm mode is the time the ocr1x register is up dated by the ocr1x buffer register, (see figure 12- 8 on page 102 and figure 12-9 on page 104 ). the pwm resolution for the phase and frequency correct pwm mode can be defined by either icr1 or ocr1a. the minimum resolution allowed is 2-bit (icr1 or ocr1a set to 0x0003), and the maximum resolution is 16-bit (icr1 or ocr1 a set to max). the pwm resolution in bits can be calculated using the following equation: f ocnxpcpwm f clk_i/o 2 ntop ?? --------------------------- - = r pfcpwm top 1 + () log 2 () log ---------------------------------- - = 104 8246b?avr?09/11 attiny2313a/4313 in phase and frequency correct pwm mode the counter is incremented until the counter value matches either the value in icr1 (wgm13:0 = 8), or the value in ocr1a (wgm13:0 = 9). the counter has then reac hed the top and ch anges the count di rection. the tcnt1 value will be equal to top for one timer clock cycle. the timing diagram for the phase correct and frequency correct pwm mode is shown on figure 12-9 on page 104 . the figure shows phase and fre- quency correct pwm mode when ocr1a or icr1 is used to define top. the tcnt1 value is in the timing diagram shown as a histogram for il lustrating the dual-slope operation. the diagram includes non-inverted and inverted pwm outputs. the small horizontal line marks on the tcnt1 slopes represent compare matc hes between ocr1x and tcnt1. the oc1x interrupt flag will be set when a compare match occurs. figure 12-9. phase and frequency correct pwm mode, timing diagram the timer/counter overflow flag (tov1) is set at the same timer clock cycle as the ocr1x registers are updated with the double buffer value (at bottom). when either ocr1a or icr1 is used for defining the top value, the ocf1a or icf1 flag set when tcnt1 has reached top. the interrupt flags can then be used to generate an interrupt each time the counter reaches the top or bottom value. when changing the top value the program must ensure that the new top value is higher or equal to the value of all of the compare registers. if the top value is lower than any of the compare registers, a compare match will neve r occur between the tcnt1 and the ocr1x. as figure 12-9 shows the output generated is, in contrast to the phase correct mode, symmetri- cal in all periods. since the ocr1x registers are updated at bottom, the length of the rising and the falling slopes will always be equal. this gives symmetrical output pulses and is therefore frequency correct. using the icr1 register for defining top work s well when using fixed top values. by using icr1, the ocr1a register is free to be used for generating a pwm output on oc1a. however, if the base pwm frequency is actively changed by changing the top value, using the ocr1a as top is clearly a better choice due to its double buffer feature. in phase and frequency correct pwm mode, the compare units allow generation of pwm wave- forms on the oc1x pins. settin g the com1x1:0 bits to two will produce a non-inverted pwm and ocrnx/top updateand tovn interrupt flag set (interrupt on bottom) ocna interrupt flag set or icfn interrupt flag set (interrupt on top) 1 2 3 4 tcntn period ocnx ocnx (comnx1:0 = 2) (comnx1:0 = 3) 105 8246b?avr?09/11 attiny2313a/4313 an inverted pwm output can be generated by setting the com1x1:0 to three (see table 12-4 on page 112 ). the actual oc1fx value will only be visible on the port pin if th e data direction for the port pin is set as output ( ddr_ocf1x). the pwm waveform is gen erated by setting (or clearing) the ocf1x register at the compare match between ocr1x and tcnt1 when the counter incre- ments, and clearing (or setting) the ocf1x register at compare match between ocr1x and tcnt1 when the counter decrements. the pw m frequency for the output when using phase and frequency correct pwm can be calculated by the following equation: the n variable represents the prescaler divider (1, 8, 64, 256, or 1024). the extreme values for the ocr1x register represents special cases when generating a pwm waveform output in the phase correct pwm mode. if the ocr1x is set equal to bottom the output will be continuously low and if set equal to top the output will be set to high for non- inverted pwm mode. for inverted pwm the output will have the opposite logic values. 12.9 timer/counter timing diagrams the timer/counter is a synchronous design and the timer clock (clk t1 ) is therefore shown as a clock enable signal in the following figures. the figures include information on when interrupt flags are set, and when the ocr1x register is updated with the ocr1x buffer value (only for modes utilizing double buffering). figure 12-10 shows a timing diagram for the setting of ocf1x. figure 12-10. timer/counter timing diagram, setting of ocf1x, no prescaling figure 12-11 shows the same timing data, but with the prescaler enabled. f ocnxpfcpwm f clk_i/o 2 ntop ?? --------------------------- - = clk tn (clk i/o /1) ocfnx clk i/o ocrnx tcntn ocrnx value ocrnx - 1 ocrnx ocrnx + 1 ocrnx + 2 106 8246b?avr?09/11 attiny2313a/4313 figure 12-11. timer/counter timing diagram, setting of ocf1x, with prescaler (f clk_i/o /8) figure 12-12 on page 106 shows the count sequence close to top in various modes. when using phase and frequency correct pwm mode the ocr1x register is updated at bottom. the timing diagrams will be the same, but top should be replaced by bottom, top-1 by bottom+1 and so on. the same renaming applies for modes that set the tov1 flag at bottom. figure 12-12. timer/counter timing diagram, no prescaling figure 12-13 shows the same timing data, but with the prescaler enabled. ocfnx ocrnx tcntn ocrnx value ocrnx - 1 ocrnx ocrnx + 1 ocrnx + 2 clk i/o clk tn (clk i/o /8) tovn (fpwm) and icfn (if used as top) ocrnx (update at top) tcntn (ctc and fpwm) tcntn (pc and pfc pwm) top - 1 top top - 1 top - 2 old ocrnx value new ocrnx value top - 1 top bottom bottom + 1 clk tn (clk i/o /1) clk i/o 107 8246b?avr?09/11 attiny2313a/4313 figure 12-13. timer/counter timing dia gram, with prescaler (f clk_i/o /8) 12.10 accessing 16-bit registers the tcnt1, ocr1a/b, and icr1 are 16-bit registers that can be accessed by the avr cpu via the 8-bit data bus. the 16-bit register must be byte accessed using two read or write operations. each 16-bit timer has a single 8-bit register for temporary storing of the high byte of the 16-bit access. the same temporary register is shared between all 16-bit registers within each 16-bit timer. accessing the low byte triggers the 16-bit read or write operation. when the low byte of a 16-bit register is written by the cpu, the high byte stored in the temporary register, and the low byte written are both copied into the 16-bit register in the same clock cycle. when the low byte of a 16-bit register is read by the cpu, the high by te of the 16-bit register is copied into the tempo- rary register in the same clock cycle as the low byte is read. not all 16-bit accesses uses the temporary register for the high byte. reading the ocr1a/b 16- bit registers does not involve using the temporary register. to do a 16-bit write, the high byte must be written before the low byte. for a 16-bit read, the low byte must be read before the high byte. the following code examples show how to access the 16-bit timer registers assuming that no interrupts updates the temporary register. the same principle can be used directly for accessing tovn (fpwm) and icf n (if used as top) ocrnx (update at top) tcntn (ctc and fpwm) tcntn (pc and pfc pwm) top - 1 top top - 1 top - 2 old ocrnx value new ocrnx value top - 1 top bottom bottom + 1 clk i/o clk tn (clk i/o /8) 108 8246b?avr?09/11 attiny2313a/4313 the ocr1a/b and icr1 registers. note that when using ?c?, the compiler handles the 16-bit access. note: 1. see ?code examples? on page 7. the assembly code example returns the tcnt1 value in the r17:r16 register pair. it is important to notice that accessing 16-bit registers are atomic operations. if an interrupt occurs between the two instructions accessing the 16-bit register, and the interrupt code updates the temporary register by accessing the same or any other of the 16-bit timer registers, then the result of the access outside the interrupt will be corrupted. therefore, when both the main code and the interrupt code update the temporary register, the main code must disable the interrupts during the 16-bit access. assembly code examples (1) ... ; set tcnt 1 to 0x01ff ldi r17,0x01 ldi r16,0xff out tcnt 1 h,r17 out tcnt 1 l,r16 ; read tcnt 1 into r17:r16 in r16,tcnt 1 l in r17,tcnt 1 h ... c code examples (1) unsigned int i; ... /* set tcnt 1 to 0x01ff */ tcnt 1 = 0x1ff; /* read tcnt 1 into i */ i = tcnt 1 ; ... 109 8246b?avr?09/11 attiny2313a/4313 the following code examples show how to do an atomic read of the tcnt1 register contents. reading any of the ocr1a/b or icr1 registers can be done by using the same principle. note: 1. see ?code examples? on page 7. the assembly code example returns the tcnt1 value in the r17:r16 register pair. assembly code example (1) tim16_readtcnt 1 : ; save global interrupt flag in r18,sreg ; disable interrupts cli ; read tcnt 1 into r17:r16 in r16,tcnt 1 l in r17,tcnt 1 h ; restore global interrupt flag out sreg,r18 ret c code example (1) unsigned int tim16_readtcnt 1 ( void ) { unsigned char sreg; unsigned int i; /* save global interrupt flag */ sreg = sreg; /* disable interrupts */ __disable_interrupt(); /* read tcnt 1 into i */ i = tcnt 1 ; /* restore global interrupt flag */ sreg = sreg; return i; } 110 8246b?avr?09/11 attiny2313a/4313 the following code examples show how to do an atomic write of the tcnt1 register contents. writing any of the ocr1a/b or icr1 register s can be done by using the same principle. note: 1. see ?code examples? on page 7. the assembly code example requires that the r17:r16 register pair contains the value to be writ- ten to tcnt1. 12.10.1 reusing the temporary high byte register if writing to more than one 16-bit register where the high byte is the same for all registers written, then the high byte only needs to be written once. however, note that the same rule of atomic operation described previously also applies in this case. assembly code example (1) tim16_writetcnt 1 : ; save global interrupt flag in r18,sreg ; disable interrupts cli ; set tcnt 1 to r17:r16 out tcnt 1 h,r17 out tcnt 1 l,r16 ; restore global interrupt flag out sreg,r18 ret c code example (1) void tim16_writetcnt 1 ( unsigned int i ) { unsigned char sreg; unsigned int i; /* save global interrupt flag */ sreg = sreg; /* disable interrupts */ __disable_interrupt(); /* set tcnt 1 to i */ tcnt 1 = i; /* restore global interrupt flag */ sreg = sreg; } 111 8246b?avr?09/11 attiny2313a/4313 12.11 register description 12.11.1 tccr1a ? timer/counter1 control register a ? bit 7:6 ? com1a1:0: compare output mode for channel a ? bit 5:4 ? com1b1:0: compare output mode for channel b the com1a1:0 and com1b1:0 control the output compare pins (oc1a and oc1b respec- tively) behavior. if one or both of the com1a1:0 bits are written to one, the oc1a output overrides the normal port functionality of the i/o pin it is connected to. if one or both of the com1b1:0 bit are written to one, the oc1b output overrides the normal port functionality of the i/o pin it is connected to. however, note that the data direction register (ddr) bit correspond- ing to the oc1a or oc1b pin must be set in order to enable the output driver. when the oc1a or oc1b is connected to the pin, the function of the com1x1:0 bits is depen- dent of the wgm13:0 bits setting. table 12-2 shows the com1x1:0 bit functionality when the wgm13:0 bits are set to a normal or a ctc mode (non-pwm). table 12-3 shows the com1x1:0 bit functionality when the wgm13:0 bits are set to the fast pwm mode. note: 1. a special case occurs when ocr1a/oc r1b equals top and com1a1/com1b1 is set. in this case the compare match is ignored, but the set or clear is done at top. see ?fast pwm mode? on page 99. for more details. bit 7 6 5 4 3210 0x2f (0x4f) com1a1 com1a0 com1b1 com1b0 ? ? wgm11 wgm10 tccr1a read/write r/w r/w r/w r/w r r r/w r/w initial value 0 0 0 0 0 0 0 0 table 12-2. compare output mode, non-pwm com1a1/com1b1 com1a0/com1b0 description 00 normal port operation, oc1a/oc1b disconnected. 0 1 toggle oc1a/oc1b on compare match. 10 clear oc1a/oc1b on compare match (set output to low level). 11 set oc1a/oc1b on compare match (set output to high level). table 12-3. compare output mode, fast pwm (1) com1a1/com1b1 com1a0/com1b0 description 00 normal port operation, oc1a/oc1b disconnected. 01 wgm13=0: normal port operation, oc1a/oc1b disconnected. wgm13=1: toggle oc1a on compare match, oc1b reserved. 10 clear oc1a/oc1b on compare match, set oc1a/oc1b at top 11 set oc1a/oc1b on compare match, clear oc1a/oc1b at top 112 8246b?avr?09/11 attiny2313a/4313 table 12-4 shows the com1x1:0 bit functionality when the wgm13:0 bits are set to the phase correct or the phase and frequency correct, pwm mode. note: 1. a special case occurs when ocr1a/ ocr1b equals top and com1a1/com1b1 is set. see ?phase correct pwm mode? on page 101. for more details. ? bit 1:0 ? wgm11:0: waveform generation mode combined with the wgm13:2 bits found in the tccr1b register, these bits control the counting sequence of the counter, the source for maximum (top) counter value, and what type of wave- form generation to be used, see table 12-5 . modes of operation supported by the timer/counter unit are: normal mode (counter), clear timer on compare match (ctc) mode, and three types of pulse width modulation (pwm) modes. ( see ?modes of operation? on page 97. ). table 12-4. compare output mode, phase correct and phase and frequency correct pwm (1) com1a1/com1b1 com1a0/com1b0 description 00 normal port operation, oc1a/oc1b disconnected. 01 wgm13=0: normal port operation, oc1a/oc1b disconnected. wgm13=1: toggle oc1a on compare match, oc1b reserved. 10 clear oc1a/oc1b on compare match when up- counting. set oc1a/oc1b on compare match when downcounting. 11 set oc1a/oc1b on compare match when up- counting. clear oc1a/oc1b on compare match when downcounting. 113 8246b?avr?09/11 attiny2313a/4313 note: 1. the ctc1 and pwm11:0 bit definition names are obsolete. use the wgm12:0 definitions. however, the functionality and location of these bits are compatible with previous versions of the timer. 12.11.2 tccr1b ? timer/counter1 control register b ? bit 7 ? icnc1: input capture noise canceler setting this bit (to one) activates the input capt ure noise canceler. when the noise canceler is activated, the input from the input capture pin (icp1) is filtered. the filter function requires four successive equal valued samples of the icp1 pin for changing its output. the input capture is therefore delayed by four oscillator cycles when the noise canceler is enabled. ? bit 6 ? ices1: input capture edge select this bit selects which edge on the input capture pin (icp1) that is used to trigger a capture event. when the ices1 bit is written to zero, a falling (negative) edge is used as trigger, and when the ices1 bit is written to one, a risi ng (positive) edge w ill trigger the capture. when a capture is triggered according to the ices1 setting, the counter value is copied into the input capture register (icr1). the event will also set the input capture flag (icf1), and this can be used to cause an input capture interrupt, if this interrupt is enabled. table 12-5. waveform generation mode bit description (1) mode wgm13 wgm12 (ctc1) wgm11 (pwm11) wgm10 (pwm10) timer/counter mode of operation top update of ocr1 x at tov1 flag set on 0 0 0 0 0 normal 0xffff immediate max 1 0 0 0 1 pwm, phase correct, 8-bit 0x00ff top bottom 2 0 0 1 0 pwm, phase correct, 9-bit 0x01ff top bottom 3 0 0 1 1 pwm, phase correct, 10-bit 0x03ff top bottom 4 0 1 0 0 ctc ocr1a immediate max 5 0 1 0 1 fast pwm, 8-bit 0x00ff top top 6 0 1 1 0 fast pwm, 9-bit 0x01ff top top 7 0 1 1 1 fast pwm, 10-bit 0x03ff top top 81000 pwm, phase and frequency correct icr1 bottom bottom 91001 pwm, phase and frequency correct ocr1a bottom bottom 10 1 0 1 0 pwm, phase correct icr1 top bottom 11 1 0 1 1 pwm, phase correct ocr1a top bottom 12 1 1 0 0 ctc icr1 immediate max 13 1 1 0 1 (reserved) ? ? ? 14 1 1 1 0 fast pwm icr1 top top 15 1 1 1 1 fast pwm ocr1a top top bit 7654 3210 0x2e (0x4e) icnc1 ices1 ? wgm13 wgm12 cs12 cs11 cs10 tccr1b read/write r/w r/w r r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 114 8246b?avr?09/11 attiny2313a/4313 when the icr1 is used as top value (see description of the wgm13:0 bits located in the tccr1a and the tccr1b register), the icp1 is disconnected and consequently the input cap- ture function is disabled. ? bit 5 ? reserved bit this bit is reserved for future use. for ensuring compatibility with future de vices, this bit must be written to zero when tccr1b is written. ? bit 4:3 ? wgm13:2: waveform generation mode see tccr1a register description. ? bit 2:0 ? cs12:0: clock select the three clock select bits select the clock source to be used by the timer/counter, see figure 12-10 on page 105 and figure 12-11 on page 106 . if external pin modes are used for the timer/counter1, transitions on the t1 pin will clock the counter even if the pin is configured as an output. this feature allows software control of the counting. 12.11.3 tccr1c ? timer/counter1 control register c ? bit 7 ? foc1a: force output compare for channel a ? bit 6 ? foc1b: force output compare for channel b the foc1a/foc1b bits are only active when the wgm13:0 bits specifies a non-pwm mode. however, for ensuring compatibility with future devices, these bits must be set to zero when tccr1a is written when operating in a pwm mode. when writing a logical one to the foc1a/foc1b bit, an immediate compare match is forced on the waveform generation unit. the oc1a/oc1b output is changed according to its com1x1:0 bits setting. note that the foc1a/foc1b bits are implemented as strobes. therefore it is the value present in the com1x1:0 bits that determine the effect of the forced compare. table 12-6. clock select bit description cs12 cs11 cs10 description 0 0 0 no clock source (timer/counter stopped). 001clk i/o /1 (no prescaling) 010clk i/o /8 (from prescaler) 011clk i/o /64 (from prescaler) 100clk i/o /256 (from prescaler) 101clk i/o /1024 (from prescaler) 1 1 0 external clock source on t1 pin. clock on falling edge. 1 1 1 external clock source on t1 pin. clock on rising edge. bit 7654 3210 0x22 (ox42) foc1a foc1b ? ? ? ? ? ? tccr1c read/write w w r r r r r r initial value 0 0 0 0 0 0 0 0 115 8246b?avr?09/11 attiny2313a/4313 a foc1a/foc1b strobe will not generate any interrupt nor will it clear the timer in clear timer on compare match (ctc) mode using ocr1a as top. the foc1a/foc1b bits are always read as zero. 12.11.4 tcnt1h and tcnt1l ? timer/counter1 the two timer/counter i/o locations (tcnt1h and tcnt1l , combined tcnt1) give direct access, both for read and for write operations, to the timer/counter unit 16-bit counter. to ensure that both the high and low bytes are read and written simultaneously when the cpu accesses these registers, the access is perfo rmed using an 8-bit temporary high byte register (temp). this temporary register is shared by all the other 16-bit registers. see ?accessing 16-bit registers? on page 107. modifying the counter (tcnt1) while the counte r is running introduces a risk of missing a com- pare match between tcnt1 and one of the ocr1x registers. writing to the tcnt1 register blocks (removes) the compare match on the following timer clock for all compare units. 12.11.5 ocr1ah and ocr1al ? ou tput compare register 1 a 12.11.6 ocr1bh and ocr1bl ? ou tput compare register 1 b the output compare registers contain a 16-bit value that is continuously compared with the counter value (tcnt1). a match can be used to generate an output compare interrupt, or to generate a waveform output on the oc1x pin. the output compare registers are 16-bit in size. to ensure that both the high and low bytes are written simultaneously when the cp u writes to these registers, the access is performed using an 8-bit temporary high byte register (temp). this temporary register is shared by all the other 16- bit registers. see ?accessing 16-bit registers? on page 107. bit 76543210 0x2d (0x4d) tcnt1[15:8] tcnt1h 0x2c (0x4c) tcnt1[7:0] tcnt1l read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 0x2b (0x4b) ocr1a[15:8] ocr1ah 0x2a (0x4a) ocr1a[7:0] ocr1al read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 0x29 (0x49) ocr1b[15:8] ocr1bh 0x28 (0x48) ocr1b[7:0] ocr1bl read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 116 8246b?avr?09/11 attiny2313a/4313 12.11.7 icr1h and icr1l ? input capture register 1 the input capture is updated with the counter (tcnt1) value each time an event occurs on the icp1 pin (or optionally on the analog comparator output for timer/counter1). the input capture can be used for defining the counter top value. the input capture register is 16-bit in size. to ensure that both the high and low bytes are read simultaneously when the cpu accesses these regi sters, the access is performed using an 8-bit temporary high byte register (temp). this temporary register is shared by all the other 16-bit registers. see ?accessing 16-bit registers? on page 107. 12.11.8 timsk ? timer/counter interrupt mask register ? bit 7 ? toie1: timer/counter1, overflow interrupt enable when this bit is written to one, and the i-flag in the status register is set (interrupts globally enabled), the timer/counter1 overflow interrupt is enabled. the corresponding interrupt vector ( see ?interrupts? on page 48. ) is executed when the tov1 flag, located in tifr, is set. ? bit 6 ? ocie1a: timer/counter1, output compare a match interrupt enable when this bit is written to one, and the i-flag in the status register is set (interrupts globally enabled), the timer/counter1 output compare a match interrupt is enabled. the corresponding interrupt vector ( see ?interrupts? on page 48. ) is executed when the ocf1a flag, located in tifr, is set. ? bit 5 ? ocie1b: timer/counter1, output compare b match interrupt enable when this bit is written to one, and the i-flag in the status register is set (interrupts globally enabled), the timer/counter1 output compare b match interrupt is enabled. the corresponding interrupt vector ( see ?interrupts? on page 48. ) is executed when the ocf1b flag, located in tifr, is set. ? bit 3 ? icie1: timer/counter1, input capture interrupt enable when this bit is written to one, and the i-flag in the status register is set (interrupts globally enabled), the timer/counter1 input capture interrupt is enabled. the corresponding interrupt vector ( see ?interrupts? on page 48. ) is executed when the icf1 flag, located in tifr, is set. bit 76543210 0x25 (0x45) icr1[15:8] icr1h 0x24 (0x44) icr1[7:0] icr1l read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 7 6 5 4 3 2 1 0 0x39 (0x59) toie1 ocie1a ocie1b ?icie1 ocie0b toie0 ocie0a timsk read/write r/w r/w r/w r r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 117 8246b?avr?09/11 attiny2313a/4313 12.11.9 tifr ? timer/counter interrupt flag register ? bit 7 ? tov1: timer/counter1, overflow flag the setting of this flag is dependent of the wgm13:0 bits setting. in normal and ctc modes, the tov1 flag is set when the timer overflows. refer to table 12-5 on page 113 for the tov1 flag behavior when using another wgm13:0 bit setting. tov1 is automatically cleared when the timer/c ounter1 overflow interrupt vector is executed. alternatively, tov1 can be cleared by writing a logic one to its bit location. ? bit 6 ? ocf1a: timer/counter1, output compare a match flag this flag is set in the timer clock cycle afte r the counter (tcnt1) value matches the output compare register a (ocr1a). note that a forced output compare (foc 1a) strobe will not set the ocf1a flag. ocf1a is automatically cleared when the output compare match a interrupt vector is exe- cuted. alternatively, ocf1a can be cleared by writing a logic one to its bit location. ? bit 5 ? ocf1b: timer/counter1, output compare b match flag this flag is set in the timer clock cycle afte r the counter (tcnt1) value matches the output compare register b (ocr1b). note that a forced output compare (foc 1b) strobe will not set the ocf1b flag. ocf1b is automatically cleared when the output compare match b interrupt vector is exe- cuted. alternatively, ocf1b can be cleared by writing a logic one to its bit location. ? bit 3 ? icf1: timer/count er1, input capture flag this flag is set when a capture event occurs on the icp1 pin. when the input capture register (icr1) is set by the wgm13:0 to be used as the top value, the icf1 flag is set when the coun- ter reaches the top value. icf1 is automatically cleared when the input capt ure interrupt vector is executed. alternatively, icf1 can be cleared by writing a logic one to its bit location. bit 76543210 0x38 (0x58) tov1 ocf1a ocf1b ? icf1 ocf0b tov0 ocf0a tifr read/write r/w r/w r/w r r/w r/w r/w r/w initial value00000000 118 8246b?avr?09/11 attiny2313a/4313 13. timer/counter0 and ti mer/counter1 prescalers timer/counter1 and timer/counter0 share the same prescaler module, but the timer/counters can have different prescaler settings. the description below applies to both timer/counter1 and timer/counter0. 13.1 internal clock source the timer/counter can be clocked directly by the system clock (by setting the csn2:0 = 1). this provides the fastest operation, with a maximum timer/counter clock frequency equal to system clock frequency (f clk_i/o ). alternatively, one of four taps from the prescaler can be used as a clock source. the prescaled clock has a frequency of either f clk_i/o /8, f clk_i/o /64, f clk_i/o /256, or f clk_i/o /1024. 13.2 prescaler reset the prescaler is free running, i.e., operates independently of the clock select logic of the timer/counter, and it is shared by timer/counter1 and timer/counter0. since the prescaler is not affected by the timer/counter? s clock select, the state of t he prescaler will have implications for situations where a prescaled clock is used. one example of prescaling artifacts occurs when the timer is enabled and clocked by the prescaler (6 > csn2:0 > 1). the number of system clock cycles from when the timer is enabled to the first count occurs can be from 1 to n+1 system clock cycles, where n equals the prescaler divisor (8, 64, 256, or 1024). it is possible to use the prescaler reset for synchronizing the timer/counter to program execu- tion. however, care must be taken if the other timer/counter that shares the same prescaler also uses prescaling. a prescaler reset will affect the prescaler period for all timer/coun ters it is connected to. 13.3 external clock source an external clock source applied to the t1/t0 pin can be used as timer/counter clock (clk t1 /clk t0 ). the t1/t0 pin is sampled once every system clock cycle by the pin synchronization logic. the synchronized (sampled) signal is then passed through the edge detector. figure 13-1 shows a functional equivalent block diagram of the t1/t0 synchronization and edge detector logic. the registers are clocked at the po sitive edge of the internal system clock ( clk i/o ). the latch is transparent in the high period of the internal system clock. the edge detector generates one clk t1 /clk t 0 pulse for each positive (csn2:0 = 7) or negative (csn2:0 = 6) edge it detects. figure 13-1. t1/t0 pin sampling the synchronization and e dge detector logic introduces a de lay of 2.5 to 3.5 system clock cycles from an edge has been applied to the t1/t0 pin to the counter is updated. tn_sync (to clock select logic) edge detector synchronization dq dq le dq tn clk i/o 119 8246b?avr?09/11 attiny2313a/4313 enabling and disabling of the clock input must be done when t1/t0 has been stable for at least one system clock cycle, otherwise it is a risk t hat a false timer/counter clock pulse is generated. each half period of the external clock applie d must be longer than one system clock cycle to ensure correct sampling. the external clock must be guaranteed to have less than half the sys- tem clock frequency (f extclk < f clk_i/o /2) given a 50/50% duty cycle. since the edge detector uses sampling, the maximum frequency of an external clock it can detect is half the sampling fre- quency (nyquist sampling theorem). however, due to variation of the system clock frequency and duty cycle caused by oscillator source (crystal, resonator, and capacitors) tolerances, it is recommended that maximum frequency of an external clock source is less than f clk_i/o /2.5. an external clock source can not be prescaled. figure 13-2. prescaler for timer/counter0 and timer/counter1 (1) note: 1. the synchronization logic on the input pins ( t1/t0) is shown in figure 13-1 on page 118 . 13.4 register description 13.4.1 gtccr ? general timer/counter control register ? bits 7..1 ? res: reserved bits these bits are reserved bits in the atti ny2313a/4313 and will always read as zero. ? bit 0 ? psr10: prescaler reset timer/counter1 and timer/counter0 when this bit is one, timer/co unter1 and timer/counter 0 prescaler will be reset. this bit is nor- mally cleared immediately by hardware. note that timer/counter1 and timer/counter0 share the same prescaler and a reset of th is prescaler will affect both timers. psr10 clear clk t1 clk t0 t1 t0 clk i/o synchronization synchronization bit 7 6 5 4 3 2 1 0 0x23 (0x43) ? ? ? ? ? ? ?psr10gtccr read/write r r r r r r r r/w initial value 0 0 0 0 0 0 0 0 120 8246b?avr?09/11 attiny2313a/4313 14. usart 14.1 features ? full duplex operation (independent se rial receive and transmit registers) ? asynchronous or synchronous operation ? master or slave clocked synchronous operation ? high resolution baud rate generator ? supports serial frames with 5, 6, 7, 8, or 9 data bits and 1 or 2 stop bits ? odd or even parity generation and parity check supported by hardware ? data overrun detection ? framing error detection ? noise filtering includes false start bit detection and digital low pass filter ? three separate interrupts on tx complete, tx data register empty and rx complete ? multi-processor communication mode ? double speed asynchronous communication mode 14.2 overview the universal synchronous and asynchronous serial receiver and transmitter (usart) is a highly flexible serial communication device. a simplified block diagram of the usart transmitter is shown in figure 14-1 . cpu accessible i/o registers and i/o pins are shown in bold. figure 14-1. usart block diagram (1) note: 1. refer to figure 1-1 on page 2 , table 10-9 on page 68 , and table 10-6 on page 66 for usart pin placement. parity generator ubrr[h:l] udr (transmit) ucsra ucsrb ucsrc baud rate generator transmit shift register receive shift register rxd txd pin control udr (receive) pin control xck data recovery clock recovery pin control tx control rx control parity checker data bus osc sync logic clock generator transmitter receiver 121 8246b?avr?09/11 attiny2313a/4313 the dashed boxes in the block diagram separate the three main parts of the usart (listed from the top): clock generator, transmitter and receiver. control registers are shared by all units. the clock generation logic consis ts of synchronization logic fo r external clock input used by synchronous slave operation, and the baud rate generator. the xck (transfer clock) pin is only used by synchronous transfer mode. the transmitter consists of a single write buffer, a serial shift register, parity generator and control logic for handling different serial frame formats. the write buffer allows a continuous transfer of data without any delay between frames. the receiver is the most complex part of the usart module due to its clock and data recovery units. the recovery units are used for asynchronous data reception. in addition to the recovery units, the receiver includes a parity checker, control logic, a shift register and a two level receive buffer (udr). the receiver supports the same frame formats as the transmitter, and can detect frame error, data overrun and parity errors. 14.2.1 avr usart vs. avr uart ? compatibility the usart is fully compatible with the avr uart regarding: ? bit locations inside all usart registers. ? baud rate generation. ? transmitter operation. ? transmit buffer functionality. ? receiver operation. however, the receive bu ffering has two improvements that will affect the comp atibility in some special cases: ? a second buffer register has been added. the two buffer registers operate as a circular fifo buffer. therefore the udr must only be read once for each incoming data! more important is the fact that the error flags (fe and dor) and the ninth data bit (rxb8) are buffered with the data in the receive buffer. therefore the status bits must always be read before the udr register is read . otherwise the error status will be lost since the buffer state is lost. ? the receiver shift register can now act as a third buffer level. this is done by allowing the received data to remain in th e serial shift register (see figure 14-1 ) if the buffer registers are full, until a new start bit is detected. the usart is therefore more resistant to data overrun (dor) error conditions. the following control bits have changed name, but have same functionality and register location: ? chr9 is changed to ucsz2. ? or is changed to dor. 14.3 clock generation the clock generation logic generates the base clock for the transmitter and receiver. the usart supports four modes of clock operati on: normal asynchronous, double speed asyn- chronous, master synchronous and slave sy nchronous mode. the umsel bit in usart control and status register c (ucsrc) selects between asynchronous and synchronous oper- ation. double speed (asynchronous mode only) is controlled by the u2x found in the ucsra register. when using synchronous mode (umsel = 1), the data direction register for the xck 122 8246b?avr?09/11 attiny2313a/4313 pin (ddr_xck) controls whether the clock source is internal (master mode) or external (slave mode). the xck pin is only active when using synchronous mode. figure 14-2 shows a block diagram of the clock generation logic. figure 14-2. clock generation logic, block diagram signal description: txclk transmitter clock (internal signal). rxclk receiver base clock (internal signal). xcki input from xck pin (internal signal). used for synchronous slave operation. xcko clock output to xck pin (internal signal). used for synchronous master operation. fosc xtal pin frequency (system clock). 14.3.1 internal clock generation ? the baud rate generator internal clock generation is used for the as ynchronous and the synchronous master modes of operation. the description in this section refers to figure 14-2 . the usart baud rate register (ubrr) and the down-counter connected to it function as a programmable prescaler or baud rate generator. the down-counter, running at system clock (f osc ), is loaded with the ubrr value each time the counter has counted down to zero or when the ubrrl register is written. a clock is gener ated each time the counter reaches zero. this clock is the baud rate ge nerator clock output (= f osc /(ubrr+1)). the transmitter divides the baud rate generator clock output by 2, 8 or 16 depending on mode. the baud rate generator out- put is used directly by the receiver?s clock an d data recovery units. however, the recovery units use a state machine that uses 2, 8 or 16 states depending on mode set by the state of the umsel, u2x and ddr_xck bits. table 14-1 contains equations for calculating the baud rate (in bits per second) and for calculat- ing the ubrr value for each mode of operation using an internally generated clock source. prescaling down-counter /2 ubrr /4 /2 fosc ubrr+1 sync register osc xck pin txclk u2x umsel ddr_xck 0 1 0 1 xcki xcko ddr_xck rxcl k 0 1 1 0 edge detector ucpol 123 8246b?avr?09/11 attiny2313a/4313 note: 1. the baud rate is defined to be the transfer rate in bit per second (bps) baud baud rate (in bits per second, bps) f osc system oscillator clock frequency ubrr contents of the ubrrh and ubrrl registers, (0-4095) some examples of ubrr values for so me system clock frequencies are found in table 14-9 (see page 142 ). 14.3.2 double speed operation (u2x) the transfer rate can be doubled by setting the u2x bit in ucsra. setting this bit only has effect for the asynchronous operation. set this bi t to zero when using synchronous operation. setting this bit will reduce the divisor of the baud rate divider from 16 to 8, effectively doubling the transfer rate for asynchronous communication. note however that the receiver will in this case only use half the number of samples (reduced from 16 to 8) for data sampling and clock recovery, and therefore a more accurate baud rate setting and system clock are required when this mode is used. for the transmitter, there are no downsides. 14.3.3 external clock external clocking is used by the synchronous sl ave modes of operation. the description in this section refers to figure 14-2 for details. external clock input from the xck pin is sampled by a synchronization register to minimize the chance of meta-stability. the output from the synchronization register must then pass through an edge detector before it can be used by the transmitter and receiver. this process intro- duces a two cpu clock period delay and theref ore the maximum external xck clock frequency is limited by the following equation: note that f osc depends on the stability of the system clock source. it is therefore recommended to add some margin to avoid possible loss of data due to frequency variations. table 14-1. equations for calculating baud rate register setting operating mode equation for calculating baud rate (1) equation for calculating ubrr value asynchronous normal mode (u2x = 0) asynchronous double speed mode (u2x = 1) synchronous master mode baud f osc 16 ubrr 1 + () -------------------------------------- - = ubrr f osc 16 baud ----------------------- - 1 ? = baud f osc 8 ubrr 1 + () ----------------------------------- = ubrr f osc 8 baud -------------------- 1 ? = baud f osc 2 ubrr 1 + () ----------------------------------- = ubrr f osc 2 baud -------------------- 1 ? = f xck f osc 4 ----------- < 124 8246b?avr?09/11 attiny2313a/4313 14.3.4 synchronous clock operation when synchronous mode is used (umsel = 1), the xck pin will be used as either clock input (slave) or clock output (master). the dependency between the clock edges and data sampling or data change is the same. the basic principle is that data input (on rxd) is sampled at the opposite xck clock edge of the edge the data output (txd) is changed. figure 14-3. synchronous mode xck timing. the ucpol bit ucrsc selects which xck clock edge is used for data sampling and which is used for data change. as figure 14-3 shows, when ucpol is zero the data will be changed at rising xck edge and sampled at falling xck edge. if ucpol is set, the data will be changed at falling xck edge and sampl ed at rising xck edge. 14.4 frame formats a serial frame is defined to be one character of da ta bits with synchronizat ion bits (start and stop bits), and optionally a parity bi t for error checking. the usart accepts all 30 combinations of the following as valid frame formats: ? 1 start bit ? 5, 6, 7, 8, or 9 data bits ? no, even or odd parity bit ? 1 or 2 stop bits a frame starts with the start bit followed by the least significant data bit. then the next data bits, up to a total of nine, are succeeding, ending with t he most significant bit. if enabled, the parity bit is inserted after the data bits, before the stop bits. when a complete frame is transmitted, it can be directly followed by a new frame, or the communication line can be set to an idle (high) state. figure 14-4 illustrates the possible combinations of th e frame formats. bits inside brackets are optional. figure 14-4. frame formats rxd / txd xck rxd / txd xck ucpol = 0 ucpol = 1 sample sample 1 0 2 3 4 [5] [6] [7] [8] [p] st sp1 [sp2] (st / idle) (idle) frame 125 8246b?avr?09/11 attiny2313a/4313 st start bit, always low. (n) data bits (0 to 8). p parity bit. can be odd or even. sp stop bit, always high. idle no transfers on the communication line (rxd or txd). an idle line must be high. the frame format used by the usart is set by the ucsz2:0, upm1:0 and usbs bits in ucsrb and ucsrc. the receiver and transmitter use the same setting. note that changing the setting of any of these bits will corrup t all ongoing communicati on for both the rece iver and transmitter. the usart character size (ucsz2:0) bits select the number of data bits in the frame. the usart parity mode (upm1:0) bits enable and set the type of parity bit. the selection between one or two stop bits is done by the usart stop bit select (usbs) bit. the receiver ignores the second stop bit. an fe (frame error) will therefor e only be detected in the cases where the first stop bit is zero. 14.4.1 parity bit calculation the parity bit is calculated by do ing an exclusive-or of all the data bits. if odd parity is used, the result of the exclusive or is inverted. the re lation between the parity bit and data bits is as follows: p even parity bit using even parity p odd parity bit using odd parity d n data bit n of the character if used, the parity bit is located between the last data bit and first stop bit of a serial frame. 14.5 usart initialization the usart has to be initialized before any communication can take place. the initialization pro- cess normally consists of setting the baud rate, setting frame format and enabling the transmitter or the receiver depending on the usage. for interrupt driven usart operation, the global interrupt flag should be cleared (and interrupts globally disabled) when doing the initialization. before doing a re-initialization with changed baud rate or frame format, be sure that there are no ongoing transmissions during the period the regist ers are changed. the txc flag can be used to check that the transmitter has completed all transfers, and the rxc flag can be used to check that there are no unread data in the receive buffer. note that the txc flag must be cleared before each transmission (before udr is written) if it is used for this purpose. p even d n 1 ? d 3 d 2 d 1 d 0 0 p odd d n 1 ? d 3 d 2 d 1 d 0 1 = = 126 8246b?avr?09/11 attiny2313a/4313 the following simple usart initialization code examples show one assembly and one c func- tion that are equal in functionality. the exampl es assume asynchronous operation using polling (no interrupts enabled) and a fixed frame format. the baud rate is given as a function parameter. for the assembly code, the baud rate parameter is assumed to be stored in the r17:r16 registers. note: 1. see ?code examples? on page 7. more advanced initialization routines can be made that include frame format as parameters, dis- able interrupts and so on. however, many appl ications use a fixed setting of the baud and control registers, and for these types of applicati ons the initialization code can be placed directly in the main routine, or be combined with initialization code for other i/o modules. 14.6 data transmission ? the usart transmitter the usart transmitter is enabled by setting the transmit enable (txen) bit in the ucsrb register. when the transmitter is enabled, the no rmal port operation of the txd pin is overrid- den by the usart and given the function as t he transmitter?s serial output. the baud rate, mode of operation and frame format must be set up once before doing any transmissions. if syn- chronous operation is used, the clock on the xck pin will be overridden and used as transmission clock. assembly code example (1) usart_init: ; set baud rate out ubrrh, r17 out ubrrl, r16 ; enable receiver and transmitter ldi r16, (1< 130 8246b?avr?09/11 attiny2313a/4313 14.7 data reception ? the usart receiver the usart receiver is enabled by writing the receive enable (rxen) bit in the ucsrb regis- ter to one. when the receiver is enabled, the normal pin operation of the rxd pin is overridden by the usart and given the function as the re ceiver?s serial input. the baud rate, mode of operation and frame format must be set up once before any serial reception can be done. if syn- chronous operation is used, the clock on the xck pin will be used as transfer clock. 14.7.1 receiving frames with 5 to 8 data bits the receiver starts data reception when it detects a valid start bit. each bit that follows the start bit will be sampled at the ba ud rate or xck clock, and shifted into the receive shift register until the first stop bit of a frame is received. a seco nd stop bit will be ignored by the receiver. when the first stop bit is received, i.e., a complete serial frame is present in the receive shift register, the contents of the shift register will be moved into the receive buffer. the receive buffer can then be read by reading the udr i/o location. the following code example shows a simple us art receive function based on polling of the receive complete (rxc) flag. when using frames with less than eight bits the most significant bits of the data read from t he udr will be masked to zero. t he usart has to be initialized before the function can be used. note: 1. see ?code examples? on page 7. the function simply waits for data to be present in the receive buffer by checking the rxc flag, before reading the buffer and returning the value. 14.7.2 receiving frames with 9 data bits if 9-bit characters are used (ucsz=7) the ninth bit must be read from the rxb8 bit in ucsrb before reading the low bits from the udr. this rule applies to the fe, dor and upe status flags as well. read status from ucsra, then da ta from udr. reading the udr i/o location will assembly code example (1) usart_receive: ; wait for data to be received sbis ucsra, rxc rjmp usart_receive ; get and return received data from buffer in r16, udr ret c code example (1) unsigned char usart_receive( void ) { /* wait for data to be received */ while ( !(ucsra & (1< 132 8246b?avr?09/11 attiny2313a/4313 the receive function example reads all the i/o r egisters into the register file before any com- putation is done. this gives an optimal receive buffer utilization since the bu ffer location read will be free to accept new data as early as possible. 14.7.3 receive compete flag and interrupt the usart receiver has one flag that indicates the receiver state. the receive complete (rxc) flag indicates if there are unread data present in the receive buf- fer. this flag is one when unread data exist in the receive buffer, and zero when the receive buffer is empty (i.e., does not contain any unread data). if the receiver is disabled (rxen = 0), the receive buffer will be flushed and consequently the rxc bit will become zero. when the receive complete interrupt enable (rxcie) in ucsrb is set, the usart receive complete interrupt will be executed as long as the rxc flag is set (provided that global inter- rupts are enabled). when interrupt-driven data reception is used, the receive complete routine must read the received data fr om udr in order to clear the rx c flag, otherwise a new interrupt will occur once the interr upt routine terminates. 14.7.4 receiver error flags the usart receiver has three error flags: frame error (fe), data overrun (dor) and parity error (upe). all can be accessed by reading ucsra. common for the error flags is that they are located in the receive buffer together with the frame for which they indicate the error status. due to the buffering of the error flags, the ucsra must be read before the receive buffer (udr), since reading the udr i/o location changes the buffer read location. another equality for the error flags is that they can not be altered by software doing a write to the flag location. however, all flags must be set to zero when the ucsra is written for upward compatibility of future usart implementations. none of the error flags can generate interrupts. the frame error (fe) flag indicates the state of the first stop bit of the next readable frame stored in the receive buffer. the fe flag is zero when the stop bit was correctly read (as one), and the fe flag will be one when the stop bit wa s incorrect (zero). this flag can be used for detecting out-of-sync conditions, detecting break conditions and protocol handling. the fe flag is not affected by the setting of the usbs bit in ucsrc since the re ceiver ignores all, except for the first, stop bits. for co mpatibility with future device s, always set this bit to zero when writing to ucsra. the data overrun (dor) flag indicates data loss due to a receiver buffer full condition. a data overrun occurs when the receive buffer is full (two characters), it is a new character waiting in the receive shift register, and a new start bit is detected. if the dor flag is set there was one or more serial frame lost between the frame last read from udr, and the next frame read from udr. for compatibility with future devices, always write this bit to zero when writing to ucsra. the dor flag is cleared when the frame received was successfully moved from the shift regis- ter to the receive buffer. the parity error (upe) flag indicates that the next frame in the receive buffer had a parity error when received. if parity check is not enabled the upe bit w ill always be read zero. for compati- bility with future devices, always set this bi t to zero when wr iting to ucsra. fo r more details see ?parity bit calculation? on page 125 and ?parity checker? on page 132 . 14.7.5 parity checker the parity checker is active when the high usar t parity mode (upm1) bit is set. type of parity check to be performed (odd or even) is selected by the upm0 bit. when enabled, the parity 133 8246b?avr?09/11 attiny2313a/4313 checker calculates the parity of the data bits in incoming frames and compares the result with the parity bit from the serial frame. the result of the check is stored in the receive buffer together with the received data and stop bits. the parity error (upe) flag can then be read by software to check if the frame had a parity error. the upe bit is set if the next character that can be read from the receive buffer had a parity error when received and the parity checking was enabled at that point (upm1 = 1). this bit is valid until the receive buffer (udr) is read. 14.7.6 disabling the receiver in contrast to the transmitter, disabling of the receiver will be immediate. data from ongoing receptions will therefore be lost. when disabled (i.e ., the rxen is set to zero) the receiver will no longer override the normal function of the rxd port pin. the receiver buffer fifo will be flushed when the receiver is disabled. remaining data in the buffer will be lost 14.7.7 flushing the receive buffer the receiver buffer fifo will be fl ushed when the receiver is disa bled, i.e., the buffer will be emptied of its contents. unread data will be lost. if the buffer has to be flushed during normal operation, due to for instance an error condition, read the udr i/o location until the rxc flag is cleared. the following code example shows how to flush the receive buffer. note: 1. see ?code examples? on page 7. 14.8 asynchronous data reception the usart includes a clock recovery and a data recovery unit for handling asynchronous data reception. the clock recovery logic is used fo r synchronizing the internally generated baud rate clock to the incoming asynchronous serial frames at the rxd pin. the data recovery logic sam- ples and low pass filters each incoming bit, ther eby improving the noise immunity of the receiver. the asynchronous reception operational range depends on the accuracy of the inter- nal baud rate clock, the rate of the incoming frames, and the frame size in number of bits. 14.8.1 asynchronous clock recovery the clock recovery logic synchronizes internal clock to the incoming serial frames. figure 14-5 illustrates the sampling process of th e start bit of an incoming frame. the sample rate is 16 times assembly code example (1) usart_flush: sbis ucsra, rxc ret in r16, udr rjmp usart_flush c code example (1) void usart_flush( void ) { unsigned char dummy; while ( ucsra & (1< 135 8246b?avr?09/11 attiny2313a/4313 figure 14-7 shows the sampling of the stop bit and the earliest possible beginning of the start bit of the next frame. figure 14-7. stop bit sampling and ne xt start bit sampling the same majority voting is done to the stop bit as done for the other bits in the frame. if the stop bit is registered to have a logic 0 valu e, the frame error (f e) flag will be set. a new high to low transition indicating the start bit of a new frame can come right after the last of the bits used for majority voting. for normal speed mode, the first low level sample can be at point marked (a) in figure 14-7 . for double speed mode the first low level must be delayed to (b). (c) marks a stop bit of full length. the ear ly start bit detection influences the operational range of the receiver. 14.8.3 asynchronous operational range the operational range of the receiver is dependent on the mismatch between the received bit rate and the internally generated baud rate. if the transmitter is sending frames at too fast or too slow bit rates, or the internally generated baud rate of the receiver does not have a similar (see table 14-2 ) base frequency, the receiver will not be abl e to synchronize the frames to the start bit. the following equations can be used to calculate the ratio of the incoming data rate and internal receiver baud rate. d sum of character size and parity size (d = 5 to 10 bit) s samples per bit. s = 16 for normal speed mode and s = 8 for double speed mode. s f first sample number used for majority voting. s f = 8 for normal speed and s f = 4 for double speed mode. s m middle sample number used for majority voting. s m = 9 for normal speed and s m = 5 for double speed mode. r slow is the ratio of the slowest incoming data rate that can be accepted in relation to the receiver baud rate. r fast is the ratio of the fastest incoming data rate that can be accepted in relation to the receiver baud rate. table 14-2 and table 14-3 list the maximum receiver baud rate error that can be tolerated. note that normal speed mode has higher toleration of baud rate variations. 1234567 8 9 10 0/1 0/1 0/1 stop 1 123 4 5 6 0/1 rxd sample (u2x = 0) sample (u2x = 1) (a) (b) (c) r slow d 1 + () s s 1 ? ds ? s f ++ ------------------------------------------ - = r fast d 2 + () s d 1 + () ss m + ----------------------------------- = 136 8246b?avr?09/11 attiny2313a/4313 the recommendations of the maximum receiver baud rate error was made under the assump- tion that the receiver and transmitter equally divides the maximum total error. there are two possible sources fo r the receivers baud rate erro r. the receiver?s system clock (xtal) will always have some minor instabilit y over the supply voltage range and the tempera- ture range. when using a crystal to generate the system clock, this is rarely a problem, but for a resonator the system clock may differ more than 2% depending of the resonators tolerance. the second source for the error is more controllable. the baud rate generator can not always do an exact division of the system frequency to get the b aud rate wanted. in this case an ubrr value that gives an acceptable low error can be used if possible. 14.9 multi-processor communication mode setting the multi-processor communication mode (mpcm) bit in ucsra enables a filtering function of incoming frames received by the usart receiver. frames that do not contain address information will be ignored and not put in to the receive buffer. this effectively reduces the number of incoming frames that has to be handled by the cpu, in a system with multiple mcus that communicate via the same serial bus. the transmitter is unaffected by the mpcm setting, but has to be used diffe rently when it is a part of a system utilizing the multi-processor communication mode. if the receiver is set up to receive frames that contain 5 to 8 data bits, then the first stop bit indi- cates if the frame contains data or address information. if the receiver is set up for frames with nine data bits, then the ninth bit (rxb8) is used for identifying address and data frames. when table 14-2. recommended maximum receiver baud rate error for normal speed mode (u2x = 0) d # (data+parity bit) r slow (%) r fast (%) max total error (%) recommended max receiver error (%) 5 93.20 106.67 +6.67/-6.8 3.0 6 94.12 105.79 +5.79/-5.88 2.5 7 94.81 105.11 +5.11/-5.19 2.0 8 95.36 104.58 +4.58/-4.54 2.0 9 95.81 104.14 +4.14/-4.19 1.5 10 96.17 103.78 +3.78/-3.83 1.5 table 14-3. recommended maximum receiver baud rate error for double speed mode (u2x = 1) d # (data+parity bit) r slow (%) r fast (%) max total error (%) recommended max receiver error (%) 5 94.12 105.66 +5.66/-5.88 2.5 6 94.92 104.92 +4.92/-5.08 2.0 7 95.52 104,35 +4.35/-4.48 1.5 8 96.00 103.90 +3.90/-4.00 1.5 9 96.39 103.53 +3.53/-3.61 1.5 10 96.70 103.23 +3.23/-3.30 1.0 137 8246b?avr?09/11 attiny2313a/4313 the frame type bit (the first stop or the ninth bit) is one, the frame contains an address. when the frame type bit is zero the frame is a data frame. the multi-processor communication mode enables several slave mcus to receive data from a master mcu. this is done by first decoding an address frame to find out which mcu has been addressed. if a particular slave mcu has been addressed, it will rece ive the following data frames as normal, while the other slave mcus will ignore the received frames until another address frame is received. 14.9.1 using mpcm for an mcu to act as a master mcu, it can use a 9-bit character frame format (ucsz = 7). the ninth bit (txb8) must be set when an address frame (txb8 = 1) or cleared when a data frame (txb = 0) is being transmitted. the slave mcus must in this case be set to use a 9-bit character frame format. the following procedure should be used to exchange data in multi-processor communication mode: 1. all slave mcus are in multi-processor co mmunication mode (mpcm in ucsra is set). 2. the master mcu sends an address frame, and all slaves receive and read this frame. in the slave mcus, the rxc flag in ucsra will be set as normal. 3. each slave mcu reads the udr register and determines if it has been selected. if so, it clears the mpcm bit in ucsra, otherwise it waits for the next address byte and keeps the mpcm setting. 4. the addressed mcu will receive all data fram es until a new address frame is received. the other slave mcus, which still have the mp cm bit set, will ignore the data frames. 5. when the last data frame is received by the addressed mcu, the addressed mcu sets the mpcm bit and waits for a new address frame from master. the process then repeats from 2. using any of the 5- to 8-bit character frame formats is possible, but impractical since the receiver must change between using n and n+1 character frame formats. this makes full- duplex operation difficult since the transmitter a nd receiver uses the same character size set- ting. if 5- to 8-bit character frames are used, the transmitter must be set to use two stop bit (usbs = 1) since the first stop bit is used for indicating the frame type. do not use read-modify-write instructions (sbi and cbi) to set or clear the mpcm bit. the mpcm bit shares the same i/o location as the txc flag and this might accidentally be cleared when using sbi or cbi instructions. 14.10 register description 14.10.1 udr ? usart i/o data register the usart transmit data buffer register and usart receive data buffer registers share the same i/o address referred to as usart data register or udr. the transmit data buffer reg- ister (txb) will be the destination for data wri tten to the udr register location. reading the udr register location will return the contents of the receive data bu ffer register (rxb). bit 76543210 0x0c (0x2c) rxb[7:0] udr (read) 0x0c (0x2c) txb[7:0] udr (write) read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 138 8246b?avr?09/11 attiny2313a/4313 for 5-, 6-, or 7-bit char acters the upper unu sed bits will be ignored by the transmitter and set to zero by the receiver. the transmit buffer can only be written when the udre flag in the ucsra register is set. data written to udr when the udre flag is not set, will be ignored by the usart transmitter. when data is written to the tr ansmit buffer, and the transmitter is enabled, the transm itter will load the data into the transmit shift register when the shift register is empty. then the data will be seri- ally transmitted on the txd pin. the receive buffer consists of a two level fifo . the fifo will change its state whenever the receive buffer is accessed. due to this behavior of the receive buffer, do not use read-modify- write instructions (sbi and cbi) on this location. be careful when using bit test instructions (sbic and sbis), since these also will change the state of the fifo. 14.10.2 ucsra ? usart control and status register a ? bit 7 ? rxc: usar t receive complete this flag bit is set when there are unread data in the receive buffer and cleared when the receive buffer is empty (i.e., does not contain any unread dat a). if the receiver is disabled, the receive buffer will be flushed and consequently the rx c bit will become zero. the rxc flag can be used to generate a receive complete interrupt (see description of the rxcie bit). ? bit 6 ? txc: usart transmit complete this flag bit is set when the entire frame in the transmit shift register has been shifted out and there are no new data currently present in the transm it buffer (udr). the txc flag bit is auto- matically cleared when a transmit complete interrupt is executed, or it can be cleared by writing a one to its bit location. the txc flag can generate a transmit complete interrupt (see descrip- tion of the txcie bit). ? bit 5 ? udre: usart data register empty the udre flag indicates if the transmit buffer (u dr) is ready to receive new data. if udre is one, the buffer is empty, and therefore ready to be written. the udre flag can generate a data register empty interrupt (see description of the udrie bit). udre is set after a reset to indicate that the transmitter is ready. ? bit 4 ? fe: frame error this bit is set if the next character in the receive buffer had a frame error when received. i.e., when the first stop bit of the next character in the receive buffer is zero. this bit is valid until the receive buffer (udr) is read. the fe bit is zero when the stop bit of received da ta is one. always set this bit to zero when writing to ucsra. ? bit 3 ? dor: data overrun this bit is set if a data overrun condition is detected. a data overrun occurs when the receive buffer is full (two characters), it is a new char acter waiting in the receive shift register, and a new start bit is detected. this bit is valid until the receive buffer (u dr) is read. always set this bit to zero when writing to ucsra. bit 76543210 0x0b (0x2b) rxc txc udre fe dor upe u2x mpcm ucsra read/write r r/w r r r r r/w r/w initial value00100000 139 8246b?avr?09/11 attiny2313a/4313 ? bit 2 ? upe: usart parity error this bit is set if the next character in the receive buffer had a parity error when received and the parity checking was enabled at that point (upm1 = 1). this bit is valid until the receive buffer (udr) is read. always set this bit to zero when writing to ucsra. ? bit 1 ? u2x: double the usart transmission speed this bit only has effect for the asynchronous operation. write this bit to zero when using syn- chronous operation. writing this bit to one will reduce the divisor of the baud rate divider from 16 to 8 effectively dou- bling the transfer rate for asynchronous communication. ? bit 0 ? mpcm: multi-processor communication mode this bit enables the multi-processor communication mode. when the mpcm bit is written to one, all the incoming frames received by the usart receiver that do not contain address infor- mation will be ignored. the transmitter is unaffe cted by the mpcm setting. for more detailed information see ?multi-processor communication mode? on page 136 . 14.10.3 ucsrb ? usart control and status register b ? bit 7 ? rxcie: rx complete interrupt enable writing this bit to one enables interrupt on the rxc flag. a usart receive complete interrupt will be generated only if the rxcie bi t is written to one, the global interrupt flag in sreg is writ- ten to one and the rxc bit in ucsra is set. ? bit 6 ? txcie: tx complete interrupt enable writing this bit to one enables interrupt on the txc flag. a usart transmit complete interrupt will be generated only if the txcie bit is written to one, the glo bal interrupt flag in sreg is writ- ten to one and the txc bit in ucsra is set. ? bit 5 ? udrie: usart data register empty interrupt enable writing this bit to one enables interrupt on the udre flag. a data register empty interrupt will be generated only if the udrie bit is written to one, the glob al interrupt flag in sreg is written to one and the udre bit in ucsra is set. ? bit 4 ? rxen: receiver enable writing this bit to one enables the usart receiv er. the receiver will override normal port oper- ation for the rxd pin when enabled. disabling the receiver will flush the receive buffer invalidating the fe, dor, and upe flags. ? bit 3 ? txen: transmitter enable writing this bit to one enables the usart tr ansmitter. the transmitter will override normal port operation for the txd pin when enabled. the disabling of the transmitter (writing txen to zero) will not become effective until ongo ing and pending transmissions ar e completed, i. e., when the transmit shift register and transmit buffer register do not contain data to be transmitted. when disabled, the transmitter will no longer override the txd port. bit 76543210 0x0a (0x2a) rxcie txcie udrie rxen txen ucsz2 rxb8 txb8 ucsrb read/write r/w r/w r/w r/w r/w r/w r r/w initial value00000000 140 8246b?avr?09/11 attiny2313a/4313 ? bit 2 ? ucsz2: character size the ucsz2 bits combined with the ucsz1:0 bit in ucsrc sets the number of data bits (char- acter size) in a frame the receiver and transmitter use. ? bit 1 ? rxb8: receive data bit 8 rxb8 is the ninth data bit of the received charac ter when operating with serial frames with nine data bits. must be read before reading the low bits from udr. ? bit 0 ? txb8: transmit data bit 8 txb8 is the ninth data bit in the character to be transmitted when operating with serial frames with nine data bits. must be writte n before writing the low bits to udr. 14.10.4 ucsrc ? usart control and status register c ? bits 7:6 ? umsel1:0: usart mode select these bits select the mode of oper ation of the usart as shown in table 14-4 . note: 1. for full description of the master spi mode (mspim) operation, see ?usart in spi mode? on page 146. ? bits 5:4 ? upm1:0: parity mode these bits enable and set type of parity generation and check. if enabled, the transmitter will automatically generate and send the parity of th e transmitted data bits within each frame. the receiver will generate a parity va lue for the incoming data and co mpare it to th e upm0 setting. if a mismatch is detected, the upe flag in ucsra will be set. bit 7 6 543210 0x03 (0x23) umsel1 umsel0 upm1 upm0 usbs ucsz1 ucsz0 ucpol ucsrc read/write r r/w r/w r/w r/w r/w r/w r/w initial value0 0 000110 table 14-4. umsel bit settings umsel1 umsel0 mode 0 0 asynchronous usart 0 1 synchronous usart 10reserved 1 1 master spi (mspim) (1) table 14-5. upm bits settings upm1 upm0 parity mode 00disabled 01reserved 1 0 enabled, even parity 1 1 enabled, odd parity 141 8246b?avr?09/11 attiny2313a/4313 ? bit 3 ? usbs: stop bit select this bit selects the number of stop bits to be inserted by the transmitter. the receiver ignores this setting. ? bit 2:1 ? ucsz1:0: character size the ucsz1:0 bits combined with the ucsz2 bit in ucsrb sets the number of data bits (char- acter size) in a frame the receiver and transmitter use. see table 14-7 . ? bit 0 ? ucpol: clock polarity this bit is used for synchronous mode only. write this bit to zero when asynchronous mode is used. the ucpol bit sets the relationship between data output change and data input sample, and the synchronous clock (xck). 14.10.5 ubrrl and ubrrh ? usart baud rate registers table 14-6. usbs bit settings usbs stop bit(s) 01-bit 12-bit table 14-7. ucsz bits settings ucsz2 ucsz1 ucsz0 character size 0005-bit 0016-bit 0107-bit 0118-bit 100reserved 101reserved 110reserved 1119-bit table 14-8. ucpol bit settings ucpol transmitted data changed (output of txd pin) received data sampled (input on rxd pin) 0 rising xck edge falling xck edge 1 falling xck edge rising xck edge bit 151413121110 9 8 0x02 (0x22) ? ? ? ? ubrr[11:8] ubrrh 0x09 (0x29) ubrr[7:0] ubrrl bit 76543210 read/write r r r r r/w r/w r/w r/w r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 00000000 142 8246b?avr?09/11 attiny2313a/4313 ? bit 15:12 ? reserved bits these bits are reserved for future use. for compatibility with future devices, these bit must be written to zero when ubrrh is written. ? bit 11:0 ? ubrr11:0: usart baud rate register this is a 12-bit register which contains the usart baud rate. the ubrrh contains the four most significant bits, and the ubrrl contains th e eight least significant bits of the usart baud rate. ongoing transmissions by the transmitter and receiver will be corrupted if th e baud rate is changed. writing ubrrl will tr igger an immediate update of the baud rate prescaler. 14.11 examples of ba ud rate setting for standard crystal and resonator frequencies, the most commonly used baud rates for asyn- chronous operation can be generated by using the ubrr settings, see the following tables from table 14-9 to table 14-12 . ubrr values which yield an actual baud rate differing less than 0.5% from the target baud rate, are bold in the table. higher error ratings are acceptable, but the receiver will have less noise resistance when the error ratings are high, especially for large serial frames (see ?asynchronous operational range? on page 135 ). the error values are calcu- lated using the following equation: error[%] baudrate closest match baudrate -------------------------------------------------------- 1 ? ?? ?? 100% ? = table 14-9. examples of ubrr settings for co mmonly used oscillator frequencies baud rate (bps) f osc = 1.0000 mhz f osc = 1.8432 mhz f osc = 2.0000 mhz u2x = 0 u2x = 1 u2x = 0 u2x = 1 u2x = 0 u2x = 1 ubrr error ubrr error ubrr error ubrr error ubrr error ubrr error 2400 250.2%510.2%470.0%950.0%510.2%1030.2% 4800 120.2%250.2%230.0%470.0%250.2%510.2% 9600 6 -7.0% 12 0.2% 11 0.0% 23 0.0% 12 0.2% 25 0.2% 14.4k 3 8.5% 8 -3.5% 7 0.0% 15 0.0% 8 -3.5% 16 2.1% 19.2k 2 8.5% 6 -7.0% 5 0.0% 11 0.0% 6 -7.0% 12 0.2% 28.8k 1 8.5% 3 8.5% 3 0.0% 7 0.0% 3 8.5% 8 -3.5% 38.4k 1 -18.6% 2 8.5% 2 0.0% 5 0.0% 2 8.5% 6 -7.0% 57.6k 0 8.5% 1 8.5% 1 0.0% 3 0.0% 1 8.5% 3 8.5% 76.8k ? ? 1 -18.6% 1 -25.0% 2 0.0% 1 -18.6% 2 8.5% 115.2k ? ? 0 8.5% 0 0.0% 1 0.0% 0 8.5% 1 8.5% 230.4k??????00.0%???? 250k??????????00.0% max. (1) 62.5 kbps 125 kbps 115.2 kbps 2 30.4 kbps 125 kbps 250 kbps 1. ubrr = 0, error = 0.0% 143 8246b?avr?09/11 attiny2313a/4313 table 14-10. examples of ubrr settings for commonly used oscillator frequencies (continued) baud rate (bps) f osc = 3.6864 mhz f osc = 4.0000 mhz f osc = 7.3728 mhz u2x = 0 u2x = 1 u2x = 0 u2x = 1 u2x = 0 u2x = 1 ubrr error ubrr error ubrr error ubrr error ubrr error ubrr error 2400 95 0.0% 191 0.0% 103 0.2% 207 0.2% 191 0.0% 383 0.0% 4800 47 0.0% 95 0.0% 51 0.2% 103 0.2% 95 0.0% 191 0.0% 9600 230.0%470.0%250.2%510.2%470.0%950.0% 14.4k 15 0.0% 31 0.0% 16 2.1% 34 -0.8% 31 0.0% 63 0.0% 19.2k 11 0.0% 23 0.0% 12 0.2% 25 0.2% 23 0.0% 47 0.0% 28.8k 7 0.0% 15 0.0% 8 -3.5% 16 2.1% 15 0.0% 31 0.0% 38.4k 5 0.0% 11 0.0% 6 -7.0% 12 0.2% 11 0.0% 23 0.0% 57.6k 3 0.0% 7 0.0% 3 8.5% 8 -3.5% 7 0.0% 15 0.0% 76.8k 2 0.0% 5 0.0% 2 8.5% 6 -7.0% 5 0.0% 11 0.0% 115.2k 1 0.0% 3 0.0% 1 8.5% 3 8.5% 3 0.0% 7 0.0% 230.4k 0 0.0% 1 0.0% 0 8.5% 1 8.5% 1 0.0% 3 0.0% 250k 0 -7.8% 1 -7.8% 0 0.0% 1 0.0% 1 -7.8% 3 -7.8% 0.5m ? ? 0 -7.8% ? ? 0 0.0% 0 -7.8% 1 -7.8% 1m ??????????0-7.8% max. (1) 230.4 kbps 460.8 kbps 250 kbps 0.5 mbps 460.8 kbps 921.6 kbps 1. ubrr = 0, error = 0.0% 144 8246b?avr?09/11 attiny2313a/4313 table 14-11. examples of ubrr settings for commonly used oscillator frequencies (continued) baud rate (bps) f osc = 8.0000 mhz f osc = 11.0592 mhz f osc = 14.7456 mhz u2x = 0 u2x = 1 u2x = 0 u2x = 1 u2x = 0 u2x = 1 ubrr error ubrr error ubrr error ubrr error ubrr error ubrr error 2400 207 0.2% 416 -0.1% 287 0.0% 575 0.0% 383 0.0% 767 0.0% 4800 103 0.2% 207 0.2% 143 0.0% 287 0.0% 191 0.0% 383 0.0% 9600 51 0.2% 103 0.2% 71 0.0% 143 0.0% 95 0.0% 191 0.0% 14.4k 34 -0.8% 68 0.6% 47 0.0% 95 0.0% 63 0.0% 127 0.0% 19.2k 25 0.2% 51 0.2% 35 0.0% 71 0.0% 47 0.0% 95 0.0% 28.8k 16 2.1% 34 -0.8% 23 0.0% 47 0.0% 31 0.0% 63 0.0% 38.4k 12 0.2% 25 0.2% 17 0.0% 35 0.0% 23 0.0% 47 0.0% 57.6k 8 -3.5% 16 2.1% 11 0.0% 23 0.0% 15 0.0% 31 0.0% 76.8k 6 -7.0% 12 0.2% 8 0.0% 17 0.0% 11 0.0% 23 0.0% 115.2k 3 8.5% 8 -3.5% 5 0.0% 11 0.0% 7 0.0% 15 0.0% 230.4k 1 8.5% 3 8.5% 2 0.0% 5 0.0% 3 0.0% 7 0.0% 250k 1 0.0% 3 0.0% 2 -7.8% 5 -7.8% 3 -7.8% 6 5.3% 0.5m 0 0.0% 1 0.0% ? ? 2 -7.8% 1 -7.8% 3 -7.8% 1m ? ? 0 0.0% ? ? ? ? 0 -7.8% 1 -7.8% max. (1) 0.5 mbps 1 mbps 691.2 kbps 1.3824 mbps 921.6 kbps 1.8432 mbps 1. ubrr = 0, error = 0.0% 145 8246b?avr?09/11 attiny2313a/4313 table 14-12. examples of ubrr settings for comm only used oscillator frequencies (continued) baud rate (bps) f osc = 16.0000 mhz u2x = 0 u2x = 1 ubrr error ubrr error 2400 416 -0.1% 832 0.0% 4800 207 0.2% 416 -0.1% 9600 103 0.2% 207 0.2% 14.4k 68 0.6% 138 -0.1% 19.2k 51 0.2% 103 0.2% 28.8k 34 -0.8% 68 0.6% 38.4k 25 0.2% 51 0.2% 57.6k 16 2.1% 34 -0.8% 76.8k 12 0.2% 25 0.2% 115.2k 8 -3.5% 16 2.1% 230.4k 3 8.5% 8 -3.5% 250k 3 0.0% 7 0.0% 0.5m 1 0.0% 3 0.0% 1m 0 0.0% 1 0.0% max. (1) 1. ubrr = 0, error = 0.0% 1 mbps 2 mbps 146 8246b?avr?09/11 attiny2313a/4313 15. usart in spi mode 15.1 features ? full duplex, three-wire synchronous data transfer ? master operation ? supports all four spi modes of operation (mode 0, 1, 2, and 3) ? lsb first or msb first data tran sfer (configurable data order) ? queued operation (double buffered) ? high resolution baud rate generator ? high speed operation (f xckmax = f ck /2) ? flexible interrupt generation 15.2 overview the universal synchronous and asynchronous serial receiver and transmitter (usart) can be set to a master spi compliant mode of operation. setting both umsel1:0 bits to one enables the usar t in mspim logic. in this mode of opera- tion the spi master control logic takes direct control over the usart resources. these resources include the transmitter and receiver shift register and buffers, and the baud rate gen- erator. the parity generator and checker, the data and clock recovery logic, and the rx and tx control logic is disabled. the usart rx and tx control logic is replaced by a common spi transfer control logic. however, the pin control l ogic and interrupt generation logic is identical in both modes of operation. the i/o register locations are the same in both modes. however, some of the functionality of the control registers changes when using mspim. 15.3 clock generation the clock generation logic generates the base clock for the transmitter and receiver. for usart mspim mode of operation only internal cl ock generation (i.e. master operation) is sup- ported. the data direction register for the xck pin (ddr_xck) must therefore be set to one (i.e. as output) for the usart in mspim to oper ate correctly. preferably the ddr_xck should be set up before the usart in mspim is enabled (i.e. txen and rxen bit set to one). the internal clock generation used in mspim mode is identical to the usart synchronous mas- ter mode. the baud rate or ubrr setting can therefore be calculated using the same equations, see table 15-1 : note: 1. the baud rate is defined to be the transfer rate in bit per second (bps) table 15-1. equations for calculating baud rate register setting operating mode equation for calculating baud rate (1) equation for calculating ubrrn value synchronous master mode baud f osc 2 ubrr 1 + () ----------------------------------- = ubrr f osc 2 baud -------------------- 1 ? = 147 8246b?avr?09/11 attiny2313a/4313 baud baud rate (in bits per second, bps) f osc system oscillator clock frequency ubrr contents of the ubrrh and ubrrl registers, (0-4095) 15.4 spi data modes and timing there are four combinations of xck (sck) phase an d polarity with respect to serial data, which are determined by control bits ucpha and ucpol. the data transfer timing diagrams are shown in figure 15-1 . data bits are shifted out and latched in on opposite edges of the xck sig- nal, ensuring sufficient time fo r data signals to stabilize. the ucpol and ucpha functionality is summarized in table 15-2 . note that changing the setting of any of these bits will corrupt all ongoing communication for both the receiver and transmitter. figure 15-1. ucpha and ucpol data transfer timing diagrams. 15.5 frame formats a serial frame for the mspim is defined to be one character of 8 data bits. the usart in mspim mode has two valid frame formats: ? 8-bit data with msb first ? 8-bit data with lsb first a frame starts with the least or most significant data bit. then the next data bits, up to a total of eight, are succeeding, ending with the most or least significant bit accordingly. when a complete frame is transmitted, a new frame can directly follow it, or the communication line can be set to an idle (high) state. the udord bit in ucsrc sets the frame format used by the usart in mspim mode. the receiver and transmitter use the same setting. note that changing the setting of any of these bits will corrupt all ongoin g communication for both th e receiver and transmitter. table 15-2. ucpol and ucpha functionality- ucpol ucpha spi mode leadin g edge trailing edge 0 0 0 sample (rising) setup (falling) 0 1 1 setup (rising) sample (falling) 1 0 2 sample (falling) setup (rising) 1 1 3 setup (falling) sample (rising) xck data setup (txd) data sample (rxd) xck data setup (txd) data sample (rxd) xck data setup (txd) data sample (rxd) xck data setup (txd) data sample (rxd) ucpol=0 ucpol=1 ucpha=0 ucpha=1 148 8246b?avr?09/11 attiny2313a/4313 16-bit data transfer can be achieved by writing two data bytes to udr. a uart transmit com- plete interrupt will then signal that the 16-bit value ha s been shifted out. 15.5.1 usart mspim initialization the usart in mspim mode has to be initialized before any communication can take place. the initialization process normally consists of setting the baud rate, setting master mode of operation (by setting ddr_xck to one), setting frame format and enabling the transmitter and the receiver. only the transmitter can operate independently. for interrupt driven usart opera- tion, the global interrupt flag should be clear ed (and thus interrupts globally disabled) when doing the initialization. note: to ensure immediate initialization of the xck ou tput the baud-rate register (ubrr) must be zero at the time the transmitter is enabled. contra ry to the normal mode usart operation the ubrr must then be written to the desired value after the transmitter is enabled, but before the first trans- mission is started. setting ubrr to zero before enabling the transmitter is not necessary if the initialization is done immediately after a reset since ubrr is reset to zero. before doing a re-initialization with changed baud rate, data mode, or frame format, be sure that there is no ongoing transmissions during the period the registers are changed. the txc flag can be used to check that the transmitter has completed all transfers, and the rxc flag can be used to check that there are no unread data in the receive buffer. note that the txc flag must be cleared before each transmission (before udr is written) if it is used for this purpose. the following simple usart initialization code examples show one assembly and one c func- tion that are equal in functionality. the examples assume polling (no interrupts enabled). the 149 8246b?avr?09/11 attiny2313a/4313 baud rate is given as a function parameter. for the assembly code, the baud rate parameter is assumed to be stored in the r17:r16 registers. note: 1. see ?code examples? on page 7. assembly code example (1) usart_init: clr r18 out ubrrh,r18 out ubrrl,r18 ; setting the xck port pin as output, enables master mode. sbi xck_ddr, xck ; set mspi mode of operation and spi data mode 0. ldi r18, (1< 151 8246b?avr?09/11 attiny2313a/4313 note: 1. see ?code examples? on page 7. 15.6.1 transmitter and receiver flags and interrupts the rxc, txc, and udre flags and corresponding interrupts in usart in mspim mode are identical in function to the normal usart operat ion. however, the receiver error status flags (fe, dor, and pe) are not in use and is always read as zero. 15.6.2 disabling the transmitter or receiver the disabling of the transmitter or receiver in usart in mspim mode is identical in function to the normal usart operation. assembly code example (1) usart_mspim_transfer: ; wait for empty transmit buffer sbis ucsra, udre rjmp usart_mspim_transfer ; put data (r16) into buffer, sends the data out udr,r16 ; wait for data to be received usart_mspim_wait_rxc: sbis ucsra, rxc rjmp usart_mspim_wait_rxc ; get and return received data from buffer in r16, udr ret c code example (1) unsigned char usart_receive( void ) { /* wait for empty transmit buffer */ while ( !( ucsra & (1< 153 8246b?avr?09/11 attiny2313a/4313 15.8 register description the following section describes the registers used for spi operation using the usart. 15.8.1 udr ? usart mspim i/o data register the function and bit description of the usart data register (udr) in mspi mode is identical to normal usart operation. see ?udr ? usart i/o data register? on page 137. 15.8.2 ucsra ? usart mspim control and status register a ? bit 7 ? rxc: usar t receive complete this flag bit is set when there are unread data in the receive buffer and cleared when the receive buffer is empty (i.e., does not contain any unread dat a). if the receiver is disabled, the receive buffer will be flushed and consequently the rx c bit will become zero. the rxc flag can be used to generate a receive complete inte rrupt (see description of the rxcie bit). ? bit 6 ? txc: usart transmit complete this flag bit is set when the entire frame in the transmit shift register has been shifted out and there are no new data currently present in the transmit buffer (udr). the txc flag bit is auto- matically cleared when a transmit complete interrupt is executed, or it can be cleared by writing a one to its bit location. the txc flag can generate a transmit complete interrupt (see descrip- tion of the txcie bit). ? bit 5 ? udre: usart data register empty the udre flag indicates if the transmit buffer (udr) is ready to receive new data. if udre is one, the buffer is empty, and th erefore ready to be written. the udre flag can generate a data register empty interrupt (see description of the udrie bit). udre is set after a reset to indicate that the transmitter is ready. ? bit 4:0 ? reserved bits in mspi mode when in mspi mode, these bits are reserved for future use. fo r compatibility with future devices, these bits must be written to zero when ucsra is written. 15.8.3 ucsrb ? usart mspim control and status register b ? bit 7 ? rxcie: rx complete interrupt enable writing this bit to one enables interrupt on the rxc flag. a us art receive complete interrupt will be generated only if the rxcie bi t is written to one, the global interrupt flag in sreg is writ- ten to one and the rxc bit in ucsra is set. bit 7 6 5 4 3 2 1 0 0x0b (0x2b) rxc txc udre - - - - - ucsra read/write r r/w r r r r r r initial value 0 0 0 0 0 1 1 0 bit 7 6543210 0x0a (0x2a) rxcie txcie udrie rxen txen - - - ucsrb read/write r/w r/w r/w r/w r/w r r r initial value 0 0 0 0 0 1 1 0 154 8246b?avr?09/11 attiny2313a/4313 ? bit 6 ? txcie: tx complete interrupt enable writing this bit to one enables interrupt on the txc flag. a usart transmit complete interrupt will be generated only if the txcie bit is written to one, the glo bal interrupt flag in sreg is writ- ten to one and the txc bit in ucsra is set. ? bit 5 ? udrie: usart data register empty interrupt enable writing this bit to one enables interrupt on the udre flag. a da ta register empty interrupt will be generated only if the udrie bit is written to one, the glob al interrupt flag in sreg is written to one and the udre bit in ucsra is set. ? bit 4 ? rxen: receiver enable writing this bit to one enable s the usart receiver in mspim mode. the receiver will override normal port operation for the rxd pin when enabl ed. disabling the receiver will flush the receive buffer. only enabling the receiver in mspi mode (i.e. setting rxen=1 and txen=0) has no meaning since it is the transmitter that controls the transfer clock and since only master mode is supported. ? bit 3 ? txen: transmitter enable writing this bit to one enables the usart tr ansmitter. the transmitter will override normal port operation for the txd pin when enabled. the disabling of the transmitter (writing txen to zero) will not become effective until ongo ing and pending transmissions ar e completed, i. e., when the transmit shift register and transmit buffer register do not contain data to be transmitted. when disabled, the transmitter will no longer override the txd port. ? bit 2:0 ? reserved bits in mspi mode when in mspi mode, these bits are reserved for future use. fo r compatibility with future devices, these bits must be written to zero when ucsrb is written. 15.8.4 ucsrc ? usart mspim control and status register c ? bit 7:6 ? umsel1:0: usart mode select these bits select the mode of operation of the usart as shown in table 15-4 . see ?ucsrc ? usart control and status register c? on page 140 for full description of the normal usart operation. the mspim is enabled when both umsel bits are set to one. the udord, ucpha, and ucpol can be set in the same write operation where the mspim is enabled. bit 7 6 5 4 3 2 1 0 0x03 (0x23) umsel1 umsel0 - - - udord ucpha ucpol ucsrc read/write r/w r/w r r r r/w r/w r/w initial value 0 0 0 0 0 1 1 0 table 15-4. umsel bits settings umsel1 umsel0 mode 0 0 asynchronous usart 0 1 synchronous usart 1 0 reserved 1 1 master spi (mspim) 155 8246b?avr?09/11 attiny2313a/4313 ? bit 5:3 ? reserved bits in mspi mode when in mspi mode, these bits are reserved for future use. fo r compatibility with future devices, these bits must be written to zero when ucsrc is written. ? bit 2 ? udord: data order when set to one the lsb of the data word is transmitted first. when set to zero the msb of the data word is transmitted first. refer to the frame formats section page 4 for details. ? bit 1 ? ucpha: clock phase the ucpha bit setting determine if data is sampled on the leasing edge (first) or tailing (last) edge of xck. refer to the spi data modes and timing section page 4 for details. ? bit 0 ? ucpol: clock polarity the ucpol bit sets the polarity of the xck clock. the combination of the ucpol and ucpha bit settings determine the timing of the data transfer. refer to the spi data modes and timing section page 4 for details. 15.8.5 ubrrl and ubrrh ? usart mspim baud rate registers the function and bit description of the baud rate registers in mspi mode is identical to normal usart operation. see ?ubrrl and ubrrh ? usart baud rate registers? on page 141. 156 8246b?avr?09/11 attiny2313a/4313 16. usi ? universal serial interface 16.1 features ? two-wire synchronous data tr ansfer (master or slave) ? three-wire synchronous data transfer (master or slave) ? data received interrupt ? wakeup from idle mode ? in two-wire mode: wake-up from all sleep modes, including power-down mode ? two-wire start condition detect or with interr upt capability 16.2 overview the universal serial interface (usi), provides the basic hardware resources needed for serial communication. combined with a minimum of cont rol software, the usi allows significantly higher transfer rates and uses less code space than solutions based on software only. interrupts are included to minimize the processor load. a simplified block diagram of the usi is shown in figure 16-1 for actual placement of i/o pins refer to ?pinout attiny2313a/4313? on page 2 . device-specific i/o register and bit locations are listed in the ?register description? on page 163 . figure 16-1. universal serial interface, block diagram the 8-bit usi data register (usidr) contains the incoming and outgoing data. it is directly accessible via the data bus but a copy of the c ontents is also placed in the usi buffer register (usibr) where it can be retrieved later. if reading the usi data register directly, the register must be read as quickly as possible to ensure that no data is lost. the most significant bit of the usi data register is connected to one of two output pins (depend- ing on the mode configuration, see ?analog comparator? on page 168 ). there is a transparent latch between the output of the usi data register and the output pin, which delays the change data bus usipf usitc usiclk usics0 usics1 usioif usioie usidc usisif usiwm0 usiwm1 usisie bit7 two-wire clock control unit do (output only) di/sda (input/open drain) usck/scl (input/open drain) 4-bit counter usidr usisr dq le usicr clock hold tim0 comp bit0 [1] 3 0 1 2 3 0 1 2 0 1 2 usibr 157 8246b?avr?09/11 attiny2313a/4313 of data output to the opposite clock edge of the data input sampling. the serial input is always sampled from the data input (di) pin independent of the configuration. the 4-bit counter can be both read and written via the data bus, and it can generate an overflow interrupt. both the usi data register and the counter are clocked simultaneously by the same clock source. this allows the counter to count the number of bits received or transmitted and generate an interrupt when the transfer is complete. note that when an external clock source is selected the counter counts both clock edges. this means the counter registers the number of clock edges and not the number of data bits. the clock can be selected from three different sources: the usck pin, timer/counter0 compare match or from software. the two-wire clock control unit can be configured to generate an interrupt when a start condition has been detected on the two-wire bus. it can also be set to generate wait states by holding the clock pin low after a start condition is detected, or after the counter overflows. 16.3 functional descriptions 16.3.1 three-wire mode the usi three-wire mode is compliant to the serial peripheral interface (spi) mode 0 and 1, but does not have the slave select (ss) pin functionality. however, this feature can be implemented in software if necessary. pin names used by this mode are: di, do, and usck. figure 16-2. three-wire mode operat ion, simplified diagram figure 16-2 shows two usi units operating in three-wire mode, one as master and one as slave. the two usi data registers are interconnected in such way that after eight usck clocks, the data in each register has been interchanged. the same clock also increments the usi?s 4-bit counter. the counter overflow (interrupt) flag, or usioif, can therefore be used to determine when a transfer is completed. the clock is generated by the master device software by toggling the usck pin via the porta register or by writing a one to bit usitc bit in usicr. slave master bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0 do di usck bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0 do di usck portxn 158 8246b?avr?09/11 attiny2313a/4313 figure 16-3. three-wire mode, timing diagram the three-wire mode timing is shown in figure 16-3 at the top of the figure is a usck cycle ref- erence. one bit is shifted into the usi data register (usidr) for eac h of these cycles. the usck timing is shown for both external clock modes. in external clock mode 0 (usics0 = 0), di is sampled at positive edges, and do is changed (u si data register is shifted by one) at nega- tive edges. in external clock mode 1 (usics0 = 1) the opposite edges with respect to mode 0 are used. in other words, data is sampled at negative and output is changed at positive edges. the usi clock modes corresponds to the spi data mode 0 and 1. referring to the timing diagram ( figure 16-3 ), a bus transfer involves the following steps: 1. the slave and master devices set up their data outputs and, depending on the protocol used, enable their output drivers (mark a and b). the output is set up by writing the data to be transmitted to the usi data regi ster. the output is enabled by setting the corresponding bit in the data direction register of port a. note that there is not a pre- ferred order of points a and b in the figure, but both must be at least one half usck cycle before point c, where the data is sampled. this is in order to ensure that the data setup requirement is satisfied. the 4-bit counter is reset to zero. 2. the master software generates a clock puls e by toggling the usck line twice (c and d). the bit values on the data input (di) pins are sampled by the usi on the first edge (c), and the data output is changed on the opposite edge (d). the 4-bit counter will count both edges. 3. step 2. is repeated eight times for a complete register (byte) transfer. 4. after eight clock pulses (i.e ., 16 clock edges) the counter w ill overflow and indicate that the transfer has been completed. if usi buffer registers are not used the data bytes that have been transferred must now be processed before a new transfer can be initi- ated. the overflow interrupt will wake up the processor if it is set to idle mode. depending on the protocol used the slav e device can now set its output to high impedance. 16.3.2 spi master operation example the following code demonstrates how to use the usi module as a spi master: spitransfer: out usidr,r16 ldi r16,(1< 159 8246b?avr?09/11 attiny2313a/4313 162 8246b?avr?09/11 attiny2313a/4313 3. the master set the first bit to be transferred and releases the scl line (c). the slave samples the data and shifts it into the usi data register at the positive edge of the scl clock. 4. after eight bits containing slave address and data direction (read or write) have been transferred, the slave counter overflows and the scl line is forced low (d). if the slave is not the one the master has addressed, it releases the scl line and waits for a new start condition. 5. when the slave is addressed, it holds the sda line low during the acknowledgment cycle before holding the scl line low again (i.e., the usi counter register must be set to 14 before releasing scl at (d)). depending on the r/w bit the master or slave enables its output. if the bit is set, a master read operation is in progress (i.e., the slave drives the sda line) the slave can hold the scl line low after the acknowledge (e). 6. multiple bytes can now be transmitted, all in same direction, until a stop condition is given by the master (f), or a new start condition is given. if the slave is not able to receive more data it does not acknowledge the data byte it has last received. when the master does a read operation it must terminate the operation by forcing the acknowledge bit low after the last byte transmitted. 16.3.5 start condition detector the start condition detector is shown in figure 16-6 . the sda line is delayed (in the range of 50 to 300 ns) to ensure valid sampling of the scl line. the start condition detector is only enabled in two-wire mode. figure 16-6. start condition detector, logic diagram the start condition detector works asynchronous ly and can therefore wake up the processor from power-down sleep mode. however, the protocol used might have restrictions on the scl hold time. therefore, w hen using this feature the oscillator st art-up time (set by cksel fuses, see ?clock sources? on page 27 ) must also be taken into consideration. refer to the description of the usisif bit on page 165 for further details. 16.3.6 clock speed considerations maximum frequency for scl and sck is f ck / 2. this is also the maximum data transmit and receive rate in both two- and three-wire mode . in two-wire slave mode the two-wire clock con- trol unit will hold the scl low unt il the slave is ready to receive more data. this may reduce the actual data rate in two-wire mode. sda scl write( usisif) clock hold usisif dq clr dq clr 163 8246b?avr?09/11 attiny2313a/4313 16.4 alternative usi usage the flexible design of the usi allows it to be used for other tasks when serial communication is not needed. below are some examples. 16.4.1 half-duplex asynchronous data transfer using the usi data register in three-wire mode it is possible to implement a more compact and higher performance uart than by software, only. 16.4.2 4-bit counter the 4-bit counter can be used as a stand-alone counter with overflow interrupt. note that if the counter is clocked externally, both cl ock edges will increment the counter value. 16.4.3 12-bit timer/counter combining the 4-bit usi counter with one of the 8-bit timer/counters creates a 12-bit counter. 16.4.4 edge triggered external interrupt by setting the counter to maximum value (f) it can function as an additional external interrupt. the overflow flag and interrupt enable bit are th en used for the external interrupt. this feature is selected by the usics1 bit. 16.4.5 software interrupt the counter overflow interrupt can be used as a software interrupt triggered by a clock strobe. 16.5 register description 16.5.1 usicr ? usi control register the usi control register includes bits for interru pt enable, setting the wire mode, selecting the clock and clock strobe. ? bit 7 ? usisie: start condition interrupt enable setting this bit to one enables the start condition detector interrupt. if there is a pending interrupt and usisie and the global interrupt enable flag are set to one the interrupt will be executed immediately. refer to the usisif bit description on page 165 for further details. ? bit 6 ? usioie: counter overflow interrupt enable setting this bit to one enables the counter overflow interrupt. if there is a pending interrupt and usioie and the global interrup t enable flag are set to one th e interrupt will be executed imme- diately. refer to the usioif bit description on page 166 for further details. ? bit 5:4 ? usiwm1:0: wire mode these bits set the type of wire mode to be used, as shown in table 16-1 on page 164 . basically, only the function of the outputs are affected by these bits. data and clock inputs are not affected by t he mode selected and will always have th e same function. the counter and usi bit 7654 3210 0x0d (0x2d) usisie usioie usiwm1 usiwm0 us ics1 usics0 usiclk usitc usicr read/write r/w r/w r/w r/w r/w r/w w w initial value 0 0 0 0 0 0 0 0 164 8246b?avr?09/11 attiny2313a/4313 data register can therefore be clocked externally and data input sampled, even when outputs are disabled. note: 1. the di and usck pins are renamed to serial data (sda) and serial clock (scl) respectively to avoid confusion between the modes of operation. ? bit 3:2 ? usics1:0: clock source select these bits set the clock source for the usi data register and counter. the data output latch ensures that the output is changed at the opposite edge of the sampling of the data input (di/sda) when using external clock source (usck/scl). when software strobe or timer/counter0 compare match clock option is selected, the output latch is transparent and therefore the output is changed immediately. clearing the usics1:0 bits enables software strobe option. when using this option, writing a one to the usiclk bit clocks both the usi data register and the counter. for external clock source (usics1 = 1), the usiclk bit is no longer used as a strobe, but selects between external clocking and software clocking by the usitc strobe bit. table 16-1. relationship between usiwm1:0 and usi operation usiwm1 usiwm0 description 00 outputs, clock hold, and start detector disabled. port pins operate as normal. 01 three-wire mode. uses do, di, and usck pins. the data output (do) pin overrides the corresponding bit in the porta register. however, the corresponding ddra bit still controls the data direction. when the port pin is set as input the pi n pull-up is controlled by the porta bit. the data input (di) and serial clock (usck) pins do not affect the normal port operation. when operating as master, clock pulses are software generated by toggling the porta register, while the da ta direction is set to output. the usitc bit in the usicr register can be used for this purpose. 10 two-wire mode. uses sda (di) and scl (usck) pins (1) . the serial data (sda) and the serial clock (scl) pins are bi-directional and use open-collector output drives. the out put drivers are enabled by setting the corresponding bit for sda and scl in the ddra register. when the output driver is enabled for the sda pin, the output driver will force the line sda low if the output of the usi data register or the corresponding bit in the porta register is zero. otherwise, the sda line will not be driven (i.e., it is released). when the scl pin output driver is enabled the scl line will be forced low if the corresponding bit in the porta register is zero, or by the start detector. otherwise the scl line will not be driven. the scl line is held low when a start de tector detects a start condition and the output is enabled. clearing the start c ondition flag (usisif) releases the line. the sda and scl pin inputs is not affected by enabling this mode. pull-ups on the sda and scl port pin are disabled in two-wire mode. 11 two-wire mode. uses sda and scl pins. same operation as in two-wire mode abo ve, except that the scl line is also held low when a counter overflow occurs, and until the counter overflow flag (usioif) is cleared. 165 8246b?avr?09/11 attiny2313a/4313 table 16-2 shows the relationship between the usics1:0 and usiclk setting and clock source used for the usi data register and the 4-bit counter. ? bit 1 ? usiclk: clock strobe writing a one to this bit location strobes the usi data register to shift one step and the counter to increment by one, provided that the software clock strobe option has been selected by writing usics1:0 bits to zero. the output will change immediately when the clock strobe is executed, i.e., during the same instruction cycle. the value shifted into the usi data register is sampled the previous instruction cycle. when an external clock source is selected (usics1 = 1), the usiclk function is changed from a clock strobe to a clock select register. setting the usiclk bit in this case will select the usitc strobe bit as clock sour ce for the 4-bit counter (see table 16-2 ). the bit will be read as zero. ? bit 0 ? usitc: toggle clock port pin writing a one to this bit location toggles the usck/s cl value either from 0 to 1, or from 1 to 0. the toggling is independent of the setting in the data direction register, but if the port value is to be shown on the pin the corresponding ddr pin must be set as output (to one). this feature allows easy clock generation when implementing master devices. when an external clock source is selected (usics 1 = 1) and the usiclk bit is set to one, writ- ing to the usitc strobe bit will directly clock th e 4-bit counter. this allows an early detection of when the transfer is done when operating as a master device. the bit will read as zero. 16.5.2 usisr ? usi status register the status register contains interrupt flags, line status flags and the counter value. ? bit 7 ? usisif: start condition interrupt flag when two-wire mode is selected, the usisif flag is set (to one) when a start condition has been detected. when three-wire mode or output disable mode has been selected any edge on the sck pin will set the flag. table 16-2. relationship between the usics1:0 and usiclk setting usics1 usics0 usiclk clock sour ce 4-bit counter clock source 0 0 0 no clock no clock 0 0 1 software clock strobe (usiclk) software clock strobe (usiclk) 0 1 x timer/counter0 compare matc h timer/counter0 compare match 1 0 0 external, positive edge external, both edges 1 1 0 external, negative edge external, both edges 1 0 1 external, positive edge software clock strobe (usitc) 1 1 1 external, negative edge software clock strobe (usitc) bit 7 6 5 4 3 2 1 0 0x0e (0x2e) usisif usioif usipf usidc usicnt3 usicnt2 usicnt1 usicnt0 usisr read/write r/w r/w r/w r r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 166 8246b?avr?09/11 attiny2313a/4313 if usisie bit in usicr and the global interrupt enable flag are set, an interrupt will be gener- ated when this flag is set. the flag will only be cl eared by writing a logical one to the usisif bit. clearing this bit will release the start detec tion hold of uscl in two-wire mode. a start condition interr upt will wakeup the processor from all sleep modes. ? bit 6 ? usioif: counter overflow interrupt flag this flag is set (one) when the 4-bit counter overfl ows (i.e., at the transition from 15 to 0). if the usioie bit in usicr and the glob al interrupt enable flag are se t an interrupt will also be gener- ated when the flag is set. the flag will only be cleared if a one is wr itten to the usioif bit. clearing this bit will release the counter overfl ow hold of scl in two-wire mode. a counter overflow interrup t will wakeup the processor from idle sleep mode. ? bit 5 ? usipf: stop condition flag when two-wire mode is selected, the usipf flag is set (one) when a stop condition has been detected. the flag is cleared by writing a one to this bit. note that this is not an interrupt flag. this signal is useful when implementing two-wire bus master arbitration. ? bit 4 ? usidc: data output collision this bit is logical one when bit 7 in the usi data register differs from the physical pin value. the flag is only valid when two-wire mode is used. th is signal is useful when implementing two-wire bus master arbitration. ? bits 3:0 ? usicnt3:0: counter value these bits reflect the current 4-bit counter value. the 4-bit counter value can directly be read or written by the cpu. the 4-bit counter increments by one for each clock generated either by the external clock edge detector, by a timer/counter0 compare match, or by software using usiclk or usitc strobe bits. the clock source depends on the setting of the usics1:0 bits. for external clock operation a special feature is added that allows the clock to be generated by writing to the usitc strobe bit. this feature is enabled by choosing an external clock source (usics1 = 1) and writing a one to the usiclk bit. note that even when no wire mode is selected (usiwm1..0 = 0) the external clock input (usck/scl) can still be used by the counter. 16.5.3 usidr ? usi data register the usi data register can be accessed directly but a copy of the data can also be found in the usi buffer register. depending on the usics1:0 bits of the usi control register a (left) shift operation may be per- formed. the shift operation can be synchronised to an external clock edge, to a timer/counter0 compare match, or directly to software via the usiclk bit. if a serial clock occurs at the same cycle the register is written, the register will c ontain the value written a nd no shift is performed. bit 7 6 5 4 3 2 1 0 0x0f (0x2f) msb lsb usidr read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 167 8246b?avr?09/11 attiny2313a/4313 note that even when no wire mode is selected (usiwm1:0 = 0) both the external data input (di/sda) and the external clock input (usck/scl) can still be used by the usi data register. the output pin (do or sda, depending on the wire mode) is connected via the output latch to the most significant bit (bit 7) of the usi data register. the output latch ensures that data input is sampled and data output is changed on opposite clock edges. the latch is open (transparent) during the first half of a serial clock cycle when an external clock source is selected (usics1 = 1) and constantly open when an internal clock s ource is used (usics1 = 0). the output will be changed immediately when a new msb is written as long as the latch is open. note that the data direction register bit corresponding to the output pin must be set to one in order to enable data output from the usi data register. 16.5.4 usibr ? usi buffer register instead of reading data from the usi data regi ster the usi buffer register can be used. this makes controlling the usi less time critical and gives the cpu more time to handle other pro- gram tasks. usi flags as set similarly as when reading the usidr register. the content of the usi data register is loaded to the usi buffer register when the transfer has been completed. bit 7 6 5 4 3 2 1 0 0x00 (0x20) msb lsb usibr read/write r r r r r r r r initial value 0 0 0 0 0 0 0 0 168 8246b?avr?09/11 attiny2313a/4313 17. analog comparator the analog comparator compares the input values on the positive pin ain0 and negative pin ain1. when the voltage on the positive pin ain0 is higher than the voltage on the negative pin ain1, the analog comparator output, aco, is set. the comparator?s output can be set to trigger the timer/counter1 input capture function. in addition, the comparator can trigger a separate interrupt, exclusive to the analog comparator. th e user can select interrupt triggering on com- parator output rise, fall or toggle. a block diagram of the comparator and its surrounding logic is shown in figure 17-1 . figure 17-1. analog comparator block diagram 17.1 register description 17.1.1 acsr ? analog comparator control and status register ? bit 7 ? acd: analog comparator disable when this bit is written logic one , the power to the analog comparator is switched off. this bit can be set at any time to tu rn off the analog com parator. this will reduce power consumption in active and idle mode. when changing the acd bit, the analog comparator interrupt must be disabled by clearing the acie bit in acsr. otherwise an interrupt can occur when the bit is changed. ? bit 6 ? acbg: analog comparator bandgap select when this bit is set, a fixed bandgap reference vo ltage replaces the positive input to the analog comparator. when this bit is cleared, ain0 is ap plied to the positive input of the analog compar- ator. when the bandgap reference is used as input to the analog comparator, it will take a certain time for the voltage to stabilize. if not stibilized, the fi rst conversion may give a wrong value. see ?internal voltage reference? on page 42. ? bit 5 ? aco: analog comparator output the output of the analog comparator is synchronized and then directly connected to aco. the synchronization introduces a delay of 1 - 2 clock cycles. acbg bandgap reference bit 76543210 0x08 (0x28) acd acbg aco aci acie acic acis1 acis0 acsr read/write r/w r/w r r/w r/w r/w r/w r/w initial value00n/a00000 169 8246b?avr?09/11 attiny2313a/4313 ? bit 4 ? aci: analog comparator interrupt flag this bit is set by hardware when a comparator output event triggers the interrupt mode defined by acis1 and acis0. the analog comparator interr upt routine is executed if the acie bit is set and the i-bit in sreg is set. aci is cleared by hardware when executing the corresponding inter- rupt handling vector. alternatively, aci is cleared by writing a logic one to the flag. ? bit 3 ? acie: analog comparator interrupt enable when the acie bit is written logic one and the i-bi t in the status register is set, the analog com- parator interrupt is activated. when written logic zero, the interrupt is disabled. ? bit 2 ? acic: analog comparator input capture enable when written logic one, this bit enables the input capture function in timer/counter1 to be trig- gered by the analog comparator. the comparator output is in this case directly connected to the input capture front-end logic, making the compar ator utilize the noise canceler and edge select features of the timer/counter1 input capture interrupt. when written logic zero, no connection between the analog comparator and the input capture function exists. to make the comparator trigger the timer/counter1 input capture interrupt, the icie1 bit in the timer interrupt mask register (timsk) must be set. ? bits 1, 0 ? acis1, acis0: analog comparator interrupt mode select these bits determine which comparator events that trigger the analog comparator interrupt. the different settings are shown in table 17-1 . when changing the acis1/acis0 bits, the analog comparator interrupt must be disabled by clearing its interrupt enable bit in the acsr register. otherwise an interrupt can occur when the bits are changed. 17.1.2 didr ? digital input disable register ? bit 1, 0 ? ain1d, ain0d: ai n1, ain0 digita l input disable when this bit is written logic one, the digital input buffer on the ain1/0 pin is disabled. the corre- sponding pin register bit will alwa ys read as zero when this bit is set. when an analog signal is applied to the ain1/0 pin and the digital input from this pin is not needed, this bit should be writ- ten logic one to reduce power consumption in the digital input buffer. table 17-1. acis1/acis0 settings acis1 acis0 interrupt mode 0 0 comparator interrupt on output toggle. 01reserved 1 0 comparator interrupt on falling output edge. 1 1 comparator interrupt on rising output edge. bit 76543210 0x01 (0x21) ? ? ? ? ? ? ain1d ain0d didr read/writerrrrrrr/wr/w initial value00000000 170 8246b?avr?09/11 attiny2313a/4313 18. debugwire on-chip debug system 18.1 features ? complete program flow control ? emulates all on-chip func tions, both digital and analog, except reset pin ? real-time operation ? symbolic debugging support (both at c and assembler source level, or for other hlls) ? unlimited number of prog ram break points (using software break points) ? non-intrusive operation ? electrical characteristics identical to real device ? automatic configuration system ? high-speed operation ? programming of non-volatile memories 18.2 overview the debugwire on-chip debug system uses a one-wire, bi-directional interface to control the program flow, execute avr instructions in the cpu and to program the different non-volatile memories. 18.3 physical interface when the debugwire enable (dwen) fuse is programmed and lock bits are unprogrammed, the debugwire system within the target device is activated. the reset port pin is configured as a wire-and (open-drain) bi-directional i/o pin with pull-up enabled and becomes the commu- nication gateway between target and emulator. figure 18-1 shows the schematic of a target mcu, with debugwire enabled, and the emulator connector. the system clock is not affected by debugwire and will always be the clock source selected by the cksel fuses. figure 18-1. the debugwire setup dw gnd dw(reset) vcc 1.8 - 5.5v 171 8246b?avr?09/11 attiny2313a/4313 when designing a system where debugwire will be used, the following observations must be made for correct operation: ? pull-up resistor on the dw/( reset) line must be larger than 10k. however, the pull-up resistor is optional. ? connecting the reset pin directly to v cc will not work. ? capacitors inserted on the reset pin must be disconnected when using debugwire. ? all external reset sources must be disconnected. 18.4 software break points debugwire supports program memory break points by the avr break instruction. setting a break point in avr studio ? will insert a break instruction in the program memo ry. the instruc- tion replaced by the break instru ction will be stored. when program execution is continued, the stored instruction will be execut ed before continuing from the program memory. a break can be inserted manually by putting the break instruction in the program. the flash must be re-programmed each time a break point is changed. this is automatically handled by avr studio th rough the debugwire inte rface. the use of brea k points will therefore reduce the flash data retention. devices used for debugging purposes should not be shipped to end customers. 18.5 limitations of debugwire the debugwire communication pin (dw) is physica lly located on the same pin as external reset (reset). an external reset source is therefore not supported when the debugwire is enabled. the debugwire system accurately emulates all i/ o functions when running at full speed, i.e., when the program in the cpu is running. when the cpu is stopped, care must be taken while accessing some of the i/o registers via the debugger (avr studio). see the debugwire docu- mentation for detailed description of the limitations. the debugwire interface is asynchronous, whic h means that the debugger needs to synchro- nize to the system clock. if the system clock is changed by software (e.g . by writing clkps bits) communication via debugwire may fail. also, clock frequencies below 100 khz may cause communication problems. a programmed dwen fuse enable s some parts of the clock system to be running in all sleep modes. this will increase the power consumption while in sleep. thus, the dwen fuse should be disabled when debugwire is not used. 172 8246b?avr?09/11 attiny2313a/4313 18.6 register description the following section describes the registers used with the debugwire. 18.6.1 dwdr ? debugwire data register the dwdr register provides a communication channel from the running program in the mcu to the debugger. this register is only accessible by the debugwire and can therefore not be used as a general purpose register in the normal operations. bit 76543210 dwdr[7:0] dwdr read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 173 8246b?avr?09/11 attiny2313a/4313 19. self-programming 19.1 features ? self-programming enables mcu to erase, write and reprogram application memory ? efficient read-modify-write support ? lock bits allow application memory to be securely closed for further access 19.2 overview the device provides a self-programming mechanism for downloading and uploading program code by the mcu itself. self-programming can us e any available data in terface and associated protocol to read code and write (program) that code into program memory. 19.3 lock bits program memory can be protected from internal or external access. see ?lock bits? on page 178 . 19.4 self-programming the flash program memory is updated in a page by page fashion. before programming a page with the data stored in the temporary page buffer, the page must be erased. the temporary page buffer is filled one word at a time using spm and the bu ffer can be filled either before the page erase command or between a page erase and a page write operation: 1. either, fill the buffer before a page erase: a. fill temporary page buffer b. perform a page erase c. perform a page write 2. or, fill the buffer after page erase: a. perform a page erase b. fill temporary page buffer c. perform a page write if only a part of the page needs to be changed, the rest of the page must be stored (for example in the temporary page buffer) before the erase, and then be re-written. the temporary page buffer can be accessed in a random sequence. it is essential that the page address used in both the page erase and page write operation is addressing the same page. the spm instruction is disabled by default but it can be enabled by programming the selfpr- gen fuse (to ?0?). 19.4.1 addressing the flash during self-programming the z-pointer is used to address the spm commands. bit 151413121110 9 8 zh (r31) z15 z14 z13 z12 z11 z10 z9 z8 zl (r30) z7z6z5z4z3z2z1z0 76543210 174 8246b?avr?09/11 attiny2313a/4313 since the flash is organized in pages (see table 21-1 on page 184 ), the program counter can be treated as having two different sections. one sect ion, consisting of the least significant bits, is addressing the words within a page, while the most significant bits are addressing the pages. this is shown in figure 19-1 , below. figure 19-1. addressing the flash during spm variables used in figure 19-1 are explained in table 19-1 , below. note that the page erase and page write operations are addressed independently. therefore it is of major importance that the software addresses the same page in both the page erase and page write operation. table 19-1. variables used in flash addressing variable description pcpage program counter page address. selects page of words and is used with page erase and page write operations. see table 21-1 on page 184 pcmsb the most significant bit of the program counter. see table 21-1 on page 184 zpcmsb the bit in the z register that is mapp ed to pcmsb. because z[0] is not used, zpcmsb = pcmsb + 1. z register bits above zpcmsb are ignored pcword program counter word address. selects the word within a page. this is used for filling the temporary buffer and must be zero during page write operations. see table 21-1 on page 184 pagemsb the most significant bit used to address the word within one page zpagemsb the bit in the z register that is mapped to pagemsb. because z[0] is not used, zpagemsb = pagemsb + 1 program memory 0 1 15 z - register bit 0 zpagemsb word address within a page page address within the flash zpcmsb instruction word pag e pcword[pagemsb:0]: 00 01 02 pageend pag e pcword pcpage pcmsb pagemsb program counter 175 8246b?avr?09/11 attiny2313a/4313 although the least significant bit of the z-register (z0) should be zero for spm, it should be noted that the lpm instruction addresses the flash byte -by-byte and uses z0 as a byte select bit. once a programming operation is initiated, the address is latched and the z-pointer can be used for other operations. 19.4.2 page erase to execute page erase: ? set up the address in the z-pointer ? write ?00000011? to spmcsr ? execute an spm instruction within f our clock cycles after writing spmcsr the data in r1 and r0 is ignored. the page address must be written to pcpage in the z-regis- ter. other bits in the z-pointer are ignored during this operation. if an interrupt occurs during the timed sequence above the four cycle access cannot be guaran- teed. in order to ensure atomic operation interrupts should be disabled before writing to spmcsr. the cpu is halted during the page erase operation. 19.4.3 page load to write an in struction word: ? set up the address in the z-pointer ? set up the data in r1:r0 ? write ?00000001? to spmcsr ? execute an spm instruction within f our clock cycles after writing spmcsr the content of pcword in the z-register is used to address the data in the temporary buffer. the temporary buffer will au to-erase after a page wr ite operation, or by writing the rwwsre bit in spmcsr. it is also erased after a system reset. note that it is not possible to write more than one time to each address without erasing the tem- porary buffer. if the eeprom is written in the middle of an spm page load operation, all data loaded will be lost. 19.4.4 page write to execute page write: ? set up the address in the z-pointer ? write ?00000101? to spmcsr ? execute an spm instruction within f our clock cycles after writing spmcsr the data in r1 and r0 is ignored. the page address must be written to pcpage. other bits in the z-pointer must be written to zero during this operation. the cpu is halted during the page write operation. 176 8246b?avr?09/11 attiny2313a/4313 19.4.5 spmcsr can not be writte n when eeprom is programmed note that an eeprom write op eration will block al l software programmi ng to flash. reading fuses and lock bits from software will also be pr evented during the eeprom write operation. it is recommended that the user checks the status bit (eepe) in eecr and verifies that it is cleared before writing to spmcsr. 19.5 preventing fl ash corruption during periods of low v cc , the flash program can be corrupted because the supply voltage is too low for the cpu and the flash to operate properly. these issues are the same as for board level systems using the flash, and the same design solutions should be applied. a flash program corruption can be caused by two situ ations when the voltage is too low. first, a regular write sequence to the flash requires a minimum voltage to operate correctly. secondly, the cpu itself can execute instruct ions incorrectly, if the supply voltage for executing instructions is too low. flash corruption can easily be avoided by following these design recommendations (one is sufficient): 1. keep the avr reset active (low) during peri ods of insufficient po wer supply voltage. this can be done by enabling the internal brown-out detector (bod) if the operating voltage matches the detection level. if not, an external low v cc reset protection circuit can be used. if a reset occurs while a write operation is in progress, the write operation will be completed provided that the power supply voltage is sufficient. 2. keep the avr core in power-down sleep mode during periods of low v cc . this will pre- vent the cpu from attempting to decode and execute instructions, effectively protecting the spmcsr register and thus the flash from unintentional writes. 19.6 programming time fo r flash when using spm flash access is timed using the internal, calibrated 8mhz oscilla tor. typical flash programming times for the cpu are shown in table 19-2 . note: 1. min and max programming times are per individual operation. 19.7 register description 19.7.1 spmcsr ? store program memory control and status register the store program memory control and status register contains the control bits needed to con- trol the program memory operations. ? bits 7, 6 ? res: reserved bits these bits are reserved bits in the attiny2313a/4313 and always read as zero. table 19-2. spm programming time operation min (1) max (1) spm: flash page erase, flash page write, and lock bit write 3.7 ms 4.5 ms bit 76543210 0x37 (0x57) ? ? rsig ctpb rflb pgwrt pgers spmen spmcsr read/write r r r/w r/w r/w r/w r/w r/w initial value00000000 177 8246b?avr?09/11 attiny2313a/4313 ? bit 5 ? rsig: read device signature imprint table issuing an lpm inst ruction within three cycles after rsig and spmen bits have been set in spmcsr will return the selected dat a (depending on z-pointer valu e) from the device signature imprint table into the de stination register. see ?device signature imprint table? on page 180 for details. ? bit 4 ? ctpb: clear temporary page buffer if the ctpb bit is writte n while filling the temporary page bu ffer, the temporary page buffer will be cleared and the da ta will be lost. ? bit 3 ? rflb: read fuse and lock bits an lpm instruction within three cycles after rflb and spmen are set in the spmcsr register, will read either the lock bits or t he fuse bits (depending on z0 in the z-pointer) in to the destina- tion register. see ?spmcsr can not be written when eeprom is programm ed? on page 176 for details. ? bit 2 ? pgwrt: page write if this bit is written to one at the same time as spmen, the next spm instruction within four clock cycles executes page write, with the data stored in the temporary buffer. the page address is taken from the high part of the z-pointer. the data in r1 and r0 are ignored. the pgwrt bit will auto-clear upon co mpletion of a page write, or if no spm instruction is ex ecuted within four clock cycles. the cpu is halted during the entire page write operation. ? bit 1 ? pgers: page erase if this bit is written to one at the same time as spmen, the next spm instruction within four clock cycles executes page erase. the page address is taken from the high part of the z-pointer. the data in r1 and r0 are ignored. the pgers bi t will auto-clear upon comp letion of a page erase, or if no spm instruction is executed within four clock cycles. the cpu is halted during the entire page write operation. ? bit 0 ? spmen: self programming enable this bit enables the spm instruction for the next four clock cycles. if written to one together with either rsig, ctpb, rflb, pgwrt, or pgers, the following spm instruction will have a spe- cial meaning, see description abo ve. if only spmen is written, the following spm instruction will store the value in r1:r0 in the temporary page buffer addressed by the z-pointer. the lsb of the z-pointer is ignored. the spmen bit will aut o-clear upon completion of an spm instruction, or if no spm instruction is executed within four clock cycles. during page erase and page write, the spmen bit remains high until the operation is completed. writing any other combination than ?100001?, ?010001?, ?001001?, ?000101?, ?000011? or ?000001? in the lower six bits will have no effect. 178 8246b?avr?09/11 attiny2313a/4313 20. lock bits, fuse bits and device signature 20.1 lock bits attiny2313a/4313 provides the program and data memory lock bits listed in table 20-1 . notes: 1. ?1? means unprogrammed, ?0? means programmed. lock bits can be left unprogrammed (?1?) or can be programmed (?0?) to obtain the additional features listed in table 20-2 . notes: 1. ?1? means unprogrammed, ?0? means programmed. 2. program fuse bits before programming lb1 and lb2. when programming the lock bits, the mode of protection can be increased, only. writing the same, or lower, mode of protection automatically results in maximum protection. lock bits can be erased to ?1? with the chip erase command, only. the attiny2313a/4313 has no separate boot loader section. the spm instruction is enabled for the whole flash if the selfprgen fuse is programmed (?0?), otherwise it is disabled. table 20-1. lock bit byte lock bit byte bit no description see default value (1) ? 7 ? 1 (unprogrammed) ? 6 ? 1 (unprogrammed) ? 5 ? 1 (unprogrammed) ? 4 ? 1 (unprogrammed) ? 3 ? 1 (unprogrammed) ? 2 ? 1 (unprogrammed) lb2 1 lock bit below 1 (unprogrammed) lb1 0 1 (unprogrammed) table 20-2. lock bit protection modes. lock bits (1) mode of protection lb2 lb1 1 1 no memory lock features enabled 10 further programming of flash and eeprom is disabled in parallel and serial programming mode. fuse bits are locked in both serial and parallel programming mode (2) 01reserved 00 further reading and programming of flash and eeprom is disabled in parallel and serial programming mode. fuse bits are locked in both serial and parallel programming mode (2) 179 8246b?avr?09/11 attiny2313a/4313 20.2 fuse bits fuse bits are described in table 20-3 , table 20-4 , and table 20-5 . note that programmed fuses read as zero. notes: 1. programming this fuse bit wi ll change the functionality of the reset pin and render further programming via the serial interface impossible. the fuse bit can be unprogrammed using the parallel programming algorithm (see page 184 ). 2. this setting does not preserve eeprom. 3. this fuse bit is not accessible in serial programming mode. 4. this setting enables spi programming. table 20-3. extended fuse byte bit # bit name use see default value 7 ? ? 1 (unprogrammed) 6 ? ? 1 (unprogrammed) 5 ? ? 1 (unprogrammed) 4 ? ? 1 (unprogrammed) 3 ? ? 1 (unprogrammed) 2 ? ? 1 (unprogrammed) 1 ? ? 1 (unprogrammed) 0 selfprgen enables spm instruction page 173 1 (unprogrammed) table 20-4. high fuse byte bit # bit name use see default value 7 dwen enables debugwire (1) page 170 1 (unprogrammed) 6 eesave preserves eeprom memory during chip erase operation page 187 1 (unprogrammed) (2) 5 spien enables serial programming and downloading of data to device (3) 0 (programmed) (4) 4 wdton sets watchdog timer permanently on page 45 1 (unprogrammed) 3 bodlevel2 sets bod trigger level page 202 1 (unprogrammed) 2 bodlevel1 1 (unprogrammed) 1 bodlevel0 1 (unprogrammed) 0 rstdisbl disables external reset (1) page 41 1 (unprogrammed) 180 8246b?avr?09/11 attiny2313a/4313 note: 1. unprogramming this fuse at low voltages may result in overclocking. see section 22.3 on page 200 for device speed versus supply voltage. 2. this setting results in maximum start-up time for the default clock source. 3. this setting selects calibrated internal rc oscillator. fuse bits are locked when lock bit 1 (lb1) is programmed. hence, fuse bits must be pro- grammed before lock bits. fuse bits are not affected by a chip erase. 20.2.1 latching of fuses the fuse values are latched when the device enters programming mode and changes of the fuse values will have no effect until the part leaves programming mode. this does not apply to the eesave fuse, which will take effe ct once it is programmed. the fuses are also latched on power-up in normal mode. 20.3 device signature imprint table the device signature imprint table is a dedicated read only memory area used for storing miscel- laneous device information, such as the device signature and oscillator calibration data. most of this memory segment is reserved for internal use, as outlined in table 20-6 . byte addresses are used when the device itself reads the data with the lpm command. external programming devices must use word addresses. notes: 1. see section ?signature bytes? for more information. table 20-5. low fuse byte bit # bit name use see default value 7 ckdiv8 divides clock by 8 (1) page 28 0 (programmed) 6 ckout outputs system cl ock on port pin page 32 1 (unprogrammed) 5sut1 ? sets system start-up time pages 28 , 29 , and 31 1 (unprogrammed) 4 sut0 0 (programmed) (2) 3 cksel3 selects clock source page 27 0 (programmed) (3) 2 cksel2 0 (programmed) (3) 1 cksel1 1 (unprogrammed) (3) 0 cksel0 0 (programmed) (3) table 20-6. contents of device signature imprint table. word address byte address high byte 0x00 0x00 signature byte 0 (1) 0x01 calibration data for internal 8 mhz oscillator (2) 0x01 0x02 signature byte 1 (1) 0x03 calibration data for internal 4 mhz oscillator (2) 0x02 0x04 signature byte 2 (1) 0x05 ... reserved for internal use 181 8246b?avr?09/11 attiny2313a/4313 2. see section ?calibration byte? for more information. 20.3.1 calibration byte the signature area of the attiny2313a/4313 contains two bytes of calibration data for the inter- nal oscillator. the calibration data in the high byte of address 0x00 is for use with the oscillator set to 8.0 mhz operation. during reset, this byte is automatically written into the osccal regis- ter to ensure correct fr equency of the oscillator. there is a separate calibration byte for the internal oscillator in 4.0 mhz mode of operation but this data is not loaded automatically. the hardware always loads the 8.0 mhz calibration data during reset. to use separate calibration da ta for the oscillator in 4.0 mhz mode the osccal register must be updated by firmware. the calibration data for 4.0 mhz operation is located in the high byte at address 0x01 of the signature area. 20.3.2 signature bytes all atmel microcontrollers have a three-byte signature code which identifies the device. this code can be read in both serial and parallel mode, also when the device is locked. the three bytes reside in a separate address space. for the attiny2313a the signature bytes are: 1. 0x000: 0x1e (indicates manufactured by atmel). 2. 0x001: 0x91 (indicates 2kb flash memory). 3. 0x002: 0x0a (indicates attiny23 13a device when 0x001 is 0x91). for the attiny4313 the signature bytes are: 1. 0x000: 0x1e (indicates manufactured by atmel). 2. 0x001: 0x92 (indicates 4kb flash memory). 3. 0x002: 0x0d (indicates attiny 4313 device when 0x001 is 0x92). 20.4 reading lock bits, fuse bits an d signature data from software fuse and lock bits can be read by device firmwa re. programmed fuse and lock bits read zero. unprogrammed as one. see ?lock bits? on page 178 and ?fuse bits? on page 179 . in addition, firmware can also read data from the device signature imprint table. see ?device signature imprint table? on page 180 . 20.4.1 lock bit read lock bit values are returned in the destination register after an lpm instruction has been issued within three cpu cycles after rflb and spmen bits have been set in spmcsr (see page 176 ). the rflb and spmen bits automatically clear upon completion of reading the lock bits, or if no lpm instruction is executed within three cpu cycl es, or if no spm instruction is executed within four cpu cycles. when rflb and spmen are cleared lpm functions normally. to read the lock bits, follow the below procedure: 1. load the z-pointer with 0x0001. 2. set rflb and spmen bits in spmcsr. 3. issue an lpm instruction within three clock cycles. 4. read the lock bits from the lpm destination register. 182 8246b?avr?09/11 attiny2313a/4313 if successful, the contents of the destination register are as follows. see section ?parallel programming? on page 184 for more information. 20.4.2 fuse bit read the algorithm for reading fuse byte s is similar to the one described above for reading lock bits, only the addresses are different. to read the fuse low byte (flb), follow the below procedure: 1. load the z-pointer with 0x0000. 2. set rflb and spmen bits in spmcsr. 3. issue an lpm instruction within three clock cycles. 4. read the flb from the lpm destination register. if successful, the contents of the destination register are as follows. refer to table 20-5 on page 180 for a detailed description and mapping of the fuse low byte. to read the fuse high byte (fhb), simply repl ace the address in the z-pointer with 0x0003 and repeat the procedure above. if successful, the contents of the destination register are as follows. refer to table 20-4 on page 179 for detailed description and mapping of the fuse high byte. to read the fuse extended byte (feb), replace the address in the z-pointer with 0x0002 and repeat the previous procedure. if successful, t he contents of the destination register are as follows. refer to table 20-3 on page 179 for detailed description and mapping of the fuse extended byte. 20.4.3 device signature imprint table read to read the contents of the device signature imprint table, follow the below procedure: 1. load the z-pointer with the table index. 2. set rsig and spmen bits in spmcsr. 3. issue an lpm instruction within three clock cycles. bit 76543210 rd ??????lb2lb1 bit 76543210 rd flb7 flb6 flb5 flb4 flb3 flb2 flb1 flb0 bit 76543210 rd fhb7 fhb6 fhb5 fhb4 fhb3 fhb2 fhb1 fhb0 bit 76543210 rd feb7 feb6 feb5 feb4 feb3 feb2 feb1 feb0 183 8246b?avr?09/11 attiny2313a/4313 4. wait three clock cycles for spmen bits to be cleared. 5. read table data from the lpm destination register. if successful, the contents of the destination register are as described in section ?device signa- ture imprint table? on page 180 . the rsig and spmen bits will auto-clear after three cpu cycles. when rsig and spmen are cleared, lpm will work as described in the ?avr instruction set? description. see program example below. note: see ?code examples? on page 7 . assembly code example dsit_read: ; uses z-pointer as table index ldi zh, 0 ldi zl, 1 ; preload spmcsr bits into r16, then write to spmcsr ldi r16, (1< 185 8246b?avr?09/11 attiny2313a/4313 signals are described in table 21-3 , below. pins not listed in t he table are referenced by pin names. pulses are assumed to be at least 250 ns, unless otherwise noted. pins xa1 and xa0 determine the action when cl ki is given a positive pulse, as shown in table 21-5 . table 21-3. pin and signal names used in programming mode signal name pin(s) i/o function rdy/bsy pd1 o 0: device is busy programming, 1: device is ready for new command. oe pd2 i output enable (active low). wr pd3 i write pulse (active low). bs1/pagel pd4 i byte select 1 (?0? selects lo w byte, ?1? selects high byte). program memory and eeprom data page load. xa0 pd5 i xtal action bit 0 xa1/bs2 pd6 i xtal action bit 1. byte select 2 (0: low byte, 1: 2 nd high byte). data i/o pb7-0 i/o bi-directional data bus (output when oe is low). table 21-4. pin values used to enter programming mode pin symbol value xa1 prog_enable[3] 0 xa0 prog_enable[2] 0 bs1 prog_enable[1] 0 wr prog_enable[0] 0 table 21-5. xa1 and xa0 coding xa1 xa0 action when clki is pulsed 0 0 load flash or eeprom address (high or low address byte, determined by bs1) 0 1 load data (high or low data byte for flash, determined by bs1) 1 0 load command 1 1 no action, idle 186 8246b?avr?09/11 attiny2313a/4313 when pulsing wr or oe , the command loaded determines the action executed. the different command options are shown in table 21-6 . 21.2.1 enter programming mode the following algorithm puts the device in parallel (high-voltage) programming mode: 1. set prog_enable pins listed in table 21-4 on page 185 to ?0000?, reset pin and v cc to 0v. 2. apply 4.5 - 5.5v between v cc and gnd. 3. ensure that v cc reaches at least 1.8v within the next 20 s. 4. wait 20 - 60 s, and apply 11.5 - 12.5v to reset. 5. keep the prog_enable pins unchanged for at least 10s after the high-voltage has been applied to ensure the prog_enable signature has been latched. 6. wait at least 300 s before giving any parallel programming commands. 7. exit programming mode by power the device down or by bringing reset pin to 0v. if the rise time of the v cc is unable to fulfill the requiremen ts listed above, th e following alterna- tive algorithm can be used. 1. set prog_enable pins listed in table 21-4 on page 185 to ?0000?, reset pin to 0v and v cc to 0v. 2. apply 4.5 - 5.5v between v cc and gnd. 3. monitor v cc , and as soon as v cc reaches 0.9 - 1.1v, apply 11.5 - 12.5v to reset. 4. keep the prog_enable pins unchanged for at least 10s after the high-voltage has been applied to ensure the prog_enable signature has been latched. 5. wait until v cc actually reaches 4.5 -5.5v before giving any parallel programming commands. 6. exit programming mode by power the device down or by bringing reset pin to 0v. table 21-6. command byte bit coding command byte command 1000 0000 chip erase 0100 0000 write fuse bits 0010 0000 write lock bits 0001 0000 write flash 0001 0001 write eeprom 0000 1000 read signature bytes and calibration byte 0000 0100 read fuse and lock bits 0000 0010 read flash 0000 0011 read eeprom 187 8246b?avr?09/11 attiny2313a/4313 21.2.2 considerations for efficient programming loaded commands and addresses are retained in the device during programming. for efficient programming, the following should be considered. ? when writing or reading multiple memory locations, the command needs only be loaded once ? do not write the data value 0xff, since this already is the contents of the entire flash and eeprom (unless the eesave fuse is programmed) after a chip erase ? address high byte needs only be loaded before programming or reading a new 256 word window in flash or 256 byte eeprom. this also applies to reading signature bytes 21.2.3 chip erase a chip erase must be performed before the flash and/or eeprom are reprogrammed. the chip erase command will erase all flash and eeprom plus lo ck bits. if the eesave fuse is programmed, the eepr om is not erased. lock bits are not reset until the program memory has been completely erased. fuse bits are not changed. the chip erase command is loaded as follows: 1. set xa1, xa0 to ?10?. this enables command loading. 2. set bs1 to ?0?. 3. set data to ?1000 0000?. this is the command for chip erase. 4. give xtal1 a positive pulse. this loads the command. 5. give wr a negative pulse. this starts the chip erase. rdy/bsy goes low. 6. wait until rdy/bsy goes high before loading a new command. 21.2.4 programming the flash flash is organized in pages, as shown in table 21-1 on page 184 . when programming the flash, the program data is first latched into a page buffer. this allows one page of program data to be programmed simultaneously. the following procedure describes how to program the entire flash memory: a. load command ?write flash? 1. set xa1, xa0 to ?10?. this enables command loading. 2. set bs1 to ?0?. 3. set data to ?0001 0000?. this is the command for write flash. 4. give xtal1 a positive pulse. this loads the command. b. load address low byte 1. set xa1, xa0 to ?00?. this enables address loading. 2. set bs1 to ?0?. this selects low address. 3. set data = address low byte (0x00 - 0xff). 4. give xtal1 a positive pulse. this loads the address low byte. c. load data low byte 188 8246b?avr?09/11 attiny2313a/4313 1. set xa1, xa0 to ?01?. this enables data loading. 2. set data = data low byte (0x00 - 0xff). 3. give xtal1 a positive pulse. this loads the data byte. d. load data high byte 1. set bs1 to ?1?. this selects high data byte. 2. set xa1, xa0 to ?01?. this enables data loading. 3. set data = data high byte (0x00 - 0xff). 4. give xtal1 a positive pulse. this loads the data byte. e. repeat b through e unt il the entire buffer is filled or unt il all data within the page is loaded. while the lower bits in the address are mapped to words within the page, the higher bits address the pages within the flash. this is illustrated in figure 21-2 on page 189 . note that if less than eight bits are required to address words in the page (pagesize < 256), the most significant bit(s) in the address low byte are used to address the page when performing a page write. f. load address high byte 1. set xa1, xa0 to ?00?. this enables address loading. 2. set bs1 to ?1?. this selects high address. 3. set data = address high byte (0x00 - 0xff). 4. give xtal1 a positive pulse. this loads the address high byte. g. program page 1. give wr a negative pulse. this starts programming of the entire page of data. rdy/bsy goes low. 2. wait until rdy/bsy goes high (see figure 21-3 on page 189 for signal waveforms). h. repeat b through h until the entire flash is programmed or until all data has been programmed. i. end page programming 1. 1. set xa1, xa0 to ?10?. this enables command loading. 2. set data to ?0000 0000?. this is the command for no operation. 3. give xtal1 a positive pulse. this loads the command, and the internal write signals are reset. flash page addressing is illustrated in figure 21-2 , below. symbols used are described in table 19-1 on page 174 . 189 8246b?avr?09/11 attiny2313a/4313 figure 21-2. addressing the flash which is organized in pages flash programming wavefo rms are illustrated in figure 21-3 , where xx means ?don?t care? and letters refer to the programming steps described earlier. figure 21-3. programming the flash waveforms 21.2.5 programming the eeprom the eeprom is organized in pages, see table 21-2 on page 184 . when programming the eeprom, the program data is latche d into a page buffer. this al lows one page of data to be programmed simultaneously. th e programming algorithm for th e eeprom data memory is as follows (see ?programming the flash? on page 187 for details on loading command, address and data): ? a: load command ?0001 0001?. ? g: load address high byte (0x00 - 0xff). ? b: load address low byte (0x00 - 0xff). program memory word address within a page page address within the flash instruction word pag e pcword[pagemsb:0]: 00 01 02 pageend pag e pcword pcpage pcmsb pagemsb program counter rdy/bsy wr oe reset +12v pagel bs2 0x10 addr. low addr. high data data low data high addr. low data low data high xa1 xa0 bs1 xtal1 xx xx xx abcdeb cdegh f 190 8246b?avr?09/11 attiny2313a/4313 ? c: load data (0x00 - 0xff). ? j: repeat 3 throug h 4 until the entire buffer is filled. ? k: program eeprom page ? set bs1 to ?0?. ?give wr a negative pulse. this starts programming of the eeprom page. rdy/bsy goes low. ? wait until to rdy/bsy goes high before programming the next page (see figure 21- 4 for signal waveforms). eeprom programming waveforms are illustrated in figure 21-4 , where xx means ?don?t care? and letters refer to the programming steps described above. figure 21-4. eeprom programming waveforms 21.2.6 reading the flash the algorithm for reading the flash memory is as follows (see ?programming the flash? on page 187 for details on command and address loading): ? a: load command ?0000 0010?. ? g: load address high byte (0x00 - 0xff). ? b: load address low byte (0x00 - 0xff). ?set oe to ?0?, and bs1 to ?0?. the flash word low byte can now be read at data. ? set bs1 to ?1?. the flash word high byte can now be read at data. ?set oe to ?1?. 21.2.7 reading the eeprom the algorithm for reading the eeprom memory is as follows (see ?programming the flash? on page 187 for details on command and address loading): ? a: load command ?0000 0011?. ? g: load address high byte (0x00 - 0xff). rdy/bsy wr oe reset +12v pagel bs2 0x11 addr. high data addr. low data addr. low data xx xa1 xa0 bs1 xtal1 xx agbceb c el k 191 8246b?avr?09/11 attiny2313a/4313 ? b: load address low byte (0x00 - 0xff). ?set oe to ?0?, and bs1 to ?0?. the eeprom data byte can now be read at data. ?set oe to ?1?. 21.2.8 programming low fuse bits the algorithm for programming the lo w fuse bits is as follows (see ?programming the flash? on page 187 for details on command and data loading): ? a: load command ?0100 0000?. ? c: load data low byte. bit n = ?0? programs and bit n = ?1? erases the fuse bit. ?give wr a negative pulse and wait for rdy/bsy to go high. 21.2.9 programming high fuse bits the algorithm for programming the high fuse bits is as follows (see ?programming the flash? on page 187 for details on command and data loading): ? a: load command ?0100 0000?. ? c: load data low byte. bit n = ?0? programs and bit n = ?1? erases the fuse bit. ? set bs1 to ?1? and bs2 to ?0?. this selects high data byte. ?give wr a negative pulse and wait for rdy/bsy to go high. ? set bs1 to ?0?. this selects low data byte. 21.2.10 programming extended fuse bits the algorithm for programming the extended fuse bits is as follows (see ?programming the flash? on page 187 for details on command and data loading): ? a: load command ?0100 0000?. ? c: load data low byte. bit n = ?0? programs and bit n = ?1? erases the fuse bit. ? set bs1 to ?0? and bs2 to ?1?. this selects extended data byte. ?give wr a negative pulse and wait for rdy/bsy to go high. ? set bs2 to ?0?. this selects low data byte. fuse programming waveforms are illustrated in figure 21-5 , where xx means ?don?t care? and letters refer to the programming steps described above. 192 8246b?avr?09/11 attiny2313a/4313 figure 21-5. fuses programming waveforms 21.2.11 programming the lock bits the algorithm for programming the lock bits is as follows (see ?programming the flash? on page 187 for details on command and data loading): 1. a: load command ?0010 0000?. 2. c: load data low byte. bit n = ?0? programs the lock bit. if lb mode 3 is programmed (lb1 and lb2 is programmed), it is not possible to program the boot lock bits by any external programming mode. 3. give wr a negative pulse and wait for rdy/bsy to go high. the lock bits can only be cleared by executing chip erase. 21.2.12 reading fuse and lock bits the algorithm for reading fuse and lock bits is as follows (see ?programming the flash? on page 187 for details on command loading): ? a: load command ?0000 0100?. ?set oe to ?0?, bs2 to ?0? and bs1 to ?0?. the status of the fuse low bits can now be read at data (?0? means programmed). ?set oe to ?0?, bs2 to ?1? and bs1 to ?1?. the status of the fuse high bits can now be read at data (?0? means programmed). ? set oe to ?0?, bs2 to ?1?, and bs1 to ?0?. the status of the extended fuse bits can now be read at data (?0? means programmed). ?set oe to ?0?, bs2 to ?0? and bs1 to ?1?. the status of the lock bits can now be read at data (?0? means programmed). ?set oe to ?1?. fuse and lock bit mapping is illustrated in figure 21-6 , below. rdy/bsy wr oe reset +12v pagel 0x40 data data xx xa1 xa0 bs1 xtal1 ac 0x40 data xx ac write fuse low byte write fuse high byte 0x40 data xx ac write extended fuse byte bs2 193 8246b?avr?09/11 attiny2313a/4313 figure 21-6. mapping between bs1, bs2 and the fuse and lock bits during read 21.2.13 reading signature bytes the algorithm for reading the signature bytes is as follows (see ?programming the flash? on page 187 for details on command and address loading): 1. a: load command ?0000 1000?. 2. b: load address low byte (0x00 - 0x02). 3. set oe to ?0?, and bs1 to ?0?. the selected signature byte can now be read at data. 4. set oe to ?1?. 21.2.14 reading the calibration byte the algorithm for reading the calibration byte is as follows (see ?programming the flash? on page 187 for details on command and address loading): 1. a: load command ?0000 1000?. 2. b: load address low byte, 0x00. 3. set oe to ?0?, and bs1 to ?1?. the calibration byte can now be read at data. 4. set oe to ?1?. 21.3 serial programming flash and eeprom memory arrays can both be programmed using the serial spi bus while reset is pulled to gnd. the serial interface consists of pins sck, mosi (input) and miso (out- put). after reset is set low, the programming enable instruction needs to be executed before program/erase operations can be executed. serial programming si gnals and connection s are illustrated in figure 21-7 , below. the pin map- ping is listed in table 21-7 on page 195 . lock bits 0 1 bs2 fuse high byte 0 1 bs1 data fuse low byte 0 1 bs2 extended fuse byte 194 8246b?avr?09/11 attiny2313a/4313 figure 21-7. serial programming signals note: if the device is clocked by the internal oscillator there is no need to connect a clock source to the clki pin. when programming the eeprom, an auto-erase cycle is built into the self-timed programming operation and there is no need to first execute the chip erase instructi on. this applies for serial programming mode, only. the chip erase operation turns the content of every memory location in flash and eeprom arrays into 0xff. depending on cksel fuses, a va lid clock must be present. th e minimum low and high periods for the serial clock (sck) input are defined as follows: ? minimum low period of serial clock: ? when f ck < 12mhz: > 2 cpu clock cycles ? when f ck >= 12mhz: 3 cpu clock cycles ? minimum high period of serial clock: ? when f ck < 12mhz: > 2 cpu clock cycles ? when f ck >= 12mhz: 3 cpu clock cycles vcc gnd xtal1 sck miso mosi reset +1.8 - 5.5v 195 8246b?avr?09/11 attiny2313a/4313 21.3.1 pin mapping the pin mapping is listed in table 21-7 . note that not all parts use the spi pins dedicated for the internal spi interface. 21.3.2 programming algorithm when writing serial data to the attiny2313a/ 4313, data is clocked on the rising edge of sck. when reading data from the at tiny2313a/4313, data is clocke d on the falling ed ge of sck. see figure 22-6 on page 205 and figure 22-7 on page 205 for timing details. to program and verify the attiny2313a/4313 in the serial programming mode, the following sequence is recommended (see table 21-8, ?serial programming instruction set,? on page 196 ): 1. power-up sequence: apply power between v cc and gnd while reset and sck are set to ?0? ? in some systems, the programmer can not guarantee that sck is held low during power-up. in this case, reset must be given a positive pulse after sck has been set to '0'. the duration of the pulse must be at least t rst plus two cpu clock cycles. see table 22-3 on page 201 for definition of minimum pulse width on reset pin, t rst 2. wait for at least 20 ms and then enable serial programming by sending the program- ming enable serial instruction to the mosi pin 3. the serial programming instructions will no t work if the communic ation is out of syn- chronization. when in sync, the second by te (0x53) will echo ba ck when issuing the third byte of the programming enable instruction ? regardless if the echo is correct or not, all four bytes of the instruction must be transmitted ? if the 0x53 did not echo back, give reset a positive pulse and issue a new programming enable command 4. the flash is programmed one page at a time. the memory page is loaded one byte at a time by supplying the 4 lsb of the address and data together with the load program memory page instruction. ? to ensure correct loading of the page, the data low byte must be loaded before data high byte is applied for a given address ? the program memory page is stored by loading the write program memory page instruction with the 6 msb of the address ? if polling ( rdy/bsy ) is not used, the user must wait at least t wd_flash before issuing the next page. (see table 21-9 on page 197 ). accessing the serial programming interface before the flash write operation completes can result in incorrect programming. 5. the eeprom can be programmed one byte or one page at a time. table 21-7. pin mapping serial programming symbol pins i/o description mosi pb5 i serial data in miso pb6 o serial data out sck pb7 i serial clock 196 8246b?avr?09/11 attiny2313a/4313 ? a : byte programming. the eeprom array is programmed one byte at a time by supplying the a ddress and data toge ther with the write instruction. eeprom memory locations are automatically erased before new data is written. if polling (rdy/bsy ) is not used, the user must wait at least t wd_eeprom before issuing the next byte (see table 21-9 ). in a chip erased device, no 0xffs in the data file(s) need to be programmed ? b : page programming (the eeprom array is programmed one page at a time). the memory page is loaded one byte at a time by supplying the 6 lsb of the address and data together with the load eeprom memory page instruction. the eeprom memory page is stored by loading the write eeprom memory page instruction with the 7 msb of the address. when using eepr om page access on ly byte locations loaded with the load eepr om memory page instruct ion are altered and the remaining locations remain unchanged. if polling (rdy/bsy ) is not used, the user must wait at least t wd_eeprom before issuing the next byte (see table 21-9 ). in a chip erased device, no 0xff in the data file(s) need to be programmed 6. any memory location can be verified by using the read instruction, which returns the content at the selected address at the serial output pin (miso) 7. at the end of the programming session, reset can be set high to commence normal operation 8. power-off sequence (if required): set reset to ?1?, and turn v cc power off 21.3.3 programming instruction set the instruction set for serial programming is described in table 21-8 . table 21-8. serial programming instruction set instruction instruction format operation byte 1 byte 2 byte 3 byte4 programming enable 1010 1100 0101 0011 xxxx xxxx xxxx xxxx enable serial programming after reset goes low. chip erase 1010 1100 100x xxxx xxxx xxxx xxxx xxxx chip erase eeprom and flash. read program memory 0010 h 000 0000 00 aa bbbb bbbb oooo oooo read h (high or low) data o from program memory at word address a : b . load program memory page 0100 h 000 000x xxxx xxxx bbbb iiii iiii write h (high or low) data i to program memory page at word address b . data low byte must be loaded before data high byte is applied within the same address. write program memory page 0100 1100 0000 00 aa bbbb xxxx xxxx xxxx write program memory page at address a : b . read eeprom memory 1010 0000 000x xxxx x bbb bbbb oooo oooo read data o from eeprom memory at address b . write eeprom memory 1100 0000 000x xxxx x bbb bbbb iiii iiii write data i to eeprom memory at address b . load eeprom memory page (page access) 1100 0001 0000 0000 0000 00 bb iiii iiii load data i to eeprom memory page buffer. after data is loaded, program eeprom page. 197 8246b?avr?09/11 attiny2313a/4313 note: a = address high bits, b = address low bits, h = 0 - low byte, 1 - high byte, o = data out, i = data in, x = don?t care if the lsb of rdy/bsy data byte out is ?1?, a programming operation is still pending. wait until this bit returns ?0? before the ne xt instruction is carried out. within the same page, the low data byte must be loaded prior to the high data byte. after data is loaded to the page buffer, program the eeprom page. 21.4 programming time for flash and eeprom flash and eeprom wait times are listed in table 21-9 . write eeprom memory page (page access) 1100 0010 00xx xxxx x bbb bb 00 xxxx xxxx write eeprom page at address b . read lock bits 0101 1000 0000 0000 xxxx xxxx xx oo oooo read lock bits. ?0? = programmed, ?1? = unprogrammed. see table 20-1 on page 178 for details. write lock bits 1010 1100 111x xxxx xxxx xxxx 11 ii iiii write lock bits. set bits = ?0? to program lock bits. see table 20-1 on page 178 for details. read signature byte 0011 0000 000x xxxx xxxx xx bb oooo oooo read signature byte o at address b . write fuse bits 1010 1100 1010 0000 xxxx xxxx iiii iiii set bits = ?0? to program, ?1? to unprogram. write fuse high bits 1010 1100 1010 1000 xxxx xxxx iiii iiii set bits = ?0? to program, ?1? to unprogram. write extended fuse bits 1010 1100 1010 0100 xxxx xxxx xxxx xxx i set bits = ?0? to program, ?1? to unprogram. read fuse bits 0101 0000 0000 0000 xxxx xxxx oooo oooo read fuse bits. ?0? = programmed, ?1? = unprogrammed. read fuse high bits 0101 1000 0000 1000 xxxx xxxx oooo oooo read fuse high bits. ?0? = pro- grammed, ?1? = unprogrammed. read extended fuse bits 0101 0000 0000 1000 xxxx xxxx oooo oooo read extended fuse bits. ?0? = pro- grammed, ?1? = unprogrammed. read calibration byte 0011 1000 000x xxxx 0000 000 b oooo oooo read calibration byte at address b . poll rdy/bsy 1111 0000 0000 0000 xxxx xxxx xxxx xxx o if o = ?1?, a programming operation is still busy. wait until this bit returns to ?0? before applying another command. table 21-8. serial programming instruction set instruction instruction format operation byte 1 byte 2 byte 3 byte4 table 21-9. minimum wait delay before writing the next flash or eeprom location symbol minimum wait delay t wd_flash 4.5 ms t wd_eeprom 4.0 ms t wd_erase 9.0 ms t wd_fuse 4.5 ms 198 8246b?avr?09/11 attiny2313a/4313 22. electrical characteristics 22.1 absolute maximum ratings* 22.2 dc characteristics operating temperature.................................. -55 c to +125 c *notice: stresses beyond those listed under ?absolute maximum ratings? may cause permanent dam- age to the device. this is a stress rating only and functional operation of the device at these or other conditions beyond those indicated in the operational sections of th is specification is not implied. exposure to absolute maximum rating conditions for extended periods may affect device reliability. storage temperature ..................................... -65c to +150c voltage on any pin except reset with respect to ground ................................-0.5v to v cc +0.5v voltage on reset with respect to ground......-0.5v to +13.0v maximum operating voltage ............................................ 6.0v dc current per i/o pin ............................................... 40.0 ma dc current v cc and gnd pins................................ 200.0 ma t a = -40 c to 85 c, v cc = 1.8v to 5.5v (unless otherwise noted) symbol parameter condition min. typ. max. units v il input low voltage except xtal1 and reset pin v cc = 1.8v - 2.4v v cc = 2.4v - 5.5v -0.5 0.2v cc 0.3v cc v v ih input high-voltage except xtal1 and reset pins v cc = 1.8v - 2.4v v cc = 2.4v - 5.5v 0.7v cc (1) 0.6v cc (1) v cc +0.5 (2) v v il1 input low voltage xtal1 pin v cc = 1.8v - 5.5v -0.5 0.1v cc v v ih1 input high-voltage xtal1 pin v cc = 1.8v - 2.4v v cc = 2.4v - 5.5v 0.8v cc (1) 0.7v cc (1) v cc +0.5 (2) v v il2 input low voltage reset pin v cc = 1.8v - 5.5v -0.5 0.2v cc v v ih2 input high-voltage reset pin v cc = 1.8v - 5.5v 0.9v cc (1) v cc +0.5 (2) v v il3 input low voltage reset pin as i/o v cc = 1.8v - 2.4v v cc = 2.4v - 5.5v -0.5 0.2v cc 0.3v cc v v ih3 input high-voltage reset pin as i/o v cc = 1.8v - 2.4v v cc = 2.4v - 5.5v 0.7v cc (1) 0.6v cc (1) v cc +0.5 (2) v v ol output low voltage (3) (except reset pin) (5) i ol = 20 ma, v cc = 5v i ol = 10ma, v cc = 3v 0.8 0.6 v v v oh output high-voltage (4) (except reset pin) (5) i oh = -20 ma, v cc = 5v i oh = -10 ma, v cc = 3v 4.2 2.4 v v i il input leakage current i/o pin v cc = 5.5 v, p i n l o w (absolute value) 1 (6) a i ih input leakage current i/o pin v cc = 5.5 v, pin high (absolute value) 1 (6) a r rst reset pull-up resistor 30 60 k r pu i/o pin pull-up resistor 20 50 k 199 8246b?avr?09/11 attiny2313a/4313 notes: 1. ?min? means the lowest value where the pin is guaranteed to be read as high. 2. ?max? means the highest value where the pin is guaranteed to be read as low. 3. although each i/o port can sink more than the test conditions (20 ma at v cc = 5v, 10 ma at v cc = 3v) under steady state conditions (non-transient), th e following must be observed: 1] the sum of all iol, for a ll ports, should not exceed 60 ma. if iol exceeds the test condition, vol may exceed the related sp ecification. pins are not guar anteed to sink current greater than the listed test condition. 4. although each i/o port can source more than the test conditions (20 ma at v cc = 5v, 10 ma at v cc = 3v) under steady state conditions (non-transient), th e following must be observed: 1] the sum of all ioh, for a ll ports, should not exceed 60 ma. if ioh exceeds the test condition, voh ma y exceed the related specification. pins are not guaranteed to source current greater than the listed test condition. 5. the reset pin must tolerate high voltages when entering and operating in programming modes and, as a consequence, has a weak drive strength as compared to regular i/o pins. see figure 23-29 and figure 23-30 . 6. these are test limits, which account for leakage currents of the test environment. actual device leakage currents are lower. 7. values using methods described in ?minimizing power consumption? on page 36 . power reduction is enabled (prr = 0xff), the external clock is selected (cksel = 0000), an d there is no i/o drive. 8. bod disabled. i cc power supply current active 1mhz, v cc = 2v (7) 0.2 0.55 ma active 4mhz, v cc = 3v (7) 1.3 2.5 ma active 8mhz, v cc = 5v (7) 3.9 7 ma idle 1mhz, v cc = 2v (7) 0.03 0.15 ma idle 4mhz, v cc = 3v (7) 0.25 0.6 ma idle 8mhz, v cc = 5v (7) 12ma power-down mode wdt enabled, v cc = 3v (8) 410a wdt disabled, v cc = 3v (8) < 0.15 2 a t a = -40 c to 85 c, v cc = 1.8v to 5.5v (unless otherwise noted) (continued) symbol parameter condition min. typ. max. units 200 8246b?avr?09/11 attiny2313a/4313 22.3 speed the maximum operating frequency of the device is dependent on supply voltage, v cc . the rela- tionship between supply voltage and maximum operating frequency is piecewise linear, as shown in figure 22-1 . figure 22-1. maximum frequency vs. v cc 22.4 clock characteristics 22.4.1 calibrated internal rc oscillator accuracy it is possible to manua lly calibrate the internal oscillator to be more accu rate than def ault factory calibration. note that the osc illator frequency depend s on temperat ure and voltage. voltage and temperature characteristics can be found in figure 23-46 on page 229 , and figure 23-47 on page 230 . notes: 1. accuracy of oscillator frequency at calibra tion point (fixed temperature and fixed voltage). 4 mhz 1. 8 v 5.5v 4.5v 20 mhz 2.7v 10 mhz table 22-1. calibration accuracy of internal rc oscillator calibration method target frequency v cc temperature accuracy at given voltage & temperature (1) factory calibration 4.0 / 8.0mhz 3v 25 c10% user calibration fixed frequency within: 3.1 ? 4.7 mhz / 7.3 ? 9.1mhz fixed voltage within: 1.8v ? 5.5v fixed temperature within: -40 c ? 85 c 2% 201 8246b?avr?09/11 attiny2313a/4313 22.4.2 external clock drive figure 22-2. external clock drive waveform 22.5 system and reset characteristics notes: 1. when reset pin used as reset (not as i/o). 2. not tested in production. v il1 v ih1 table 22-2. external clock drive symbol parameter v cc = 1.8 - 5.5v v cc = 2.7 - 5.5v v cc = 4.5 - 5.5v units min. max. min. max. min. max. 1/t clcl clock frequency 0 4 0 10 0 20 mhz t clcl clock period 250 100 50 ns t chcx high time 100 40 20 ns t clcx low time 100 40 20 ns t clch rise time 2.0 1.6 0.5 s t chcl fall time 2.0 1.6 0.5 s t clcl change in period from one clock cycle to the next 2 2 2 % table 22-3. reset, brown-out, and internal voltage characteristics symbol parameter condi tion min typ max units v rst reset pin threshold voltage 0.2 v cc 0.8v cc v t rst minimum pulse width on reset pin (1)(2) v cc = 1.8 - 5.5v 2.5 s v hyst brown-out detector hysteresis (2) 50 mv t bod min pulse width on brown-out reset (2) 2s v bg internal bandgap reference voltage v cc = 2.7v t a =25c 1.0 1.1 1.2 v t bg internal bandgap reference start-up time (2) v cc = 2.7v t a =25c 40 70 s i bg internal bandgap reference current consumption (2) v cc = 2.7v t a =25c 15 a 202 8246b?avr?09/11 attiny2313a/4313 22.5.1 enhanced power-on reset notes: 1. values are guidelines, only. 2. threshold where device is released from reset when voltage is rising. 3. the power-on reset will not work unless the supply voltage has been below v poa . 22.5.2 brown-out detection note: 1. v bot may be below nominal minimum operating voltage for some devices. for devices where this is the case, the device is tested down to v cc = v bot during the production test. this guar- antees that a brown-out reset will occur before v cc drops to a voltage where correct operation of the microcontroller is no longer guaranteed. 22.6 analog comparat or characteristics note: all parameters are based on simulation results and they are not tested in production table 22-4. characteristics of enhanced power-on reset. t a = -40 ? 85 c symbol parameter min (1) typ (1) max (1) units v por release threshold of power-on reset (2) 1.1 1.4 1.6 v v poa activation threshold of power-on reset (3) 0.6 1.3 1.6 v sr on power-on slope rate 0.01 v/ms table 22-5. v bot vs. bodlevel fuse coding bodlevel [1:0] fuses min (1) typ (1) max (1) units 11 bod disabled 10 1.7 1.8 2.0 v 01 2.5 2.7 2.9 00 4.1 4.3 4.5 table 22-6. analog comparator characteristics, t a = -40 c - 85 c symbol parameter condi tion min typ max units v acio input offset voltage v cc = 5v, v in = v cc / 2 < 10 40 mv i aclk input leakage current v cc = 5v, v in = v cc / 2 -50 50 na t acpd analog propagation delay (from saturation to slight overdrive) v cc = 2.7v 750 ns v cc = 4.0v 500 analog propagation delay (large step change) v cc = 2.7v 100 v cc = 4.0v 75 t dpd digital propagation delay v cc = 1.8v - 5.5 1 2 clk 203 8246b?avr?09/11 attiny2313a/4313 22.7 parallel programmi ng characteristics notes: 1. t wlrh is valid for the write flash, write eeprom , write fuse bits a nd write lock bits commands. 2. t wlrh_ce is valid for the chip erase command. table 22-7. parallel programming characteristics, v cc = 5v 10% symbol parameter min typ max units v pp programming enable voltage 11.5 12.5 v i pp programming enable current 250 a t dvxh data and control valid before xtal1 high 67 ns t xlxh xtal1 low to xtal1 high 200 ns t xhxl xtal1 pulse width high 150 ns t xldx data and control hold after xtal1 low 67 ns t xlwl xtal1 low to wr low 0 ns t xlph xtal1 low to pagel high 0 ns t plxh pagel low to xtal1 high 150 ns t bvph bs1 valid before pagel high 67 ns t phpl pagel pulse width high 150 ns t plbx bs1 hold after pagel low 67 ns t wlbx bs2/1 hold after wr low 67 ns t plwl pagel low to wr low 67 ns t bvwl bs1 valid to wr low 67 ns t wlwh wr pulse width low 150 ns t wlrl wr low to rdy/bsy low 0 1 s t wlrh wr low to rdy/bsy high (1) 3.7 4.5 ms t wlrh_ce wr low to rdy/bsy high for chip erase (2) 7.5 9 ms t xlol xtal1 low to oe low 0 ns t bvdv bs1 valid to data valid 0 1000 ns t oldv oe low to data valid 1000 ns t ohdz oe high to data tri-stated 1000 ns 204 8246b?avr?09/11 attiny2313a/4313 figure 22-3. parallel programming timing, including some general timing requirements figure 22-4. parallel programming timing, loading sequence with timing requirements (1) note: 1. the timing requirements shown in figure 22-3 (i.e., t dvxh , t xhxl , and t xldx ) also apply to load- ing operation. figure 22-5. parallel programming timing, reading sequence (within the same page) with timing requirements (1) note: 1. the timing requirements shown in figure 22-3 (i.e., t dvxh , t xhxl , and t xldx ) also apply to read- ing operation. data & contol (data, xa0/1, bs1, bs2) xtal1 t xhxl t wlwh t dvxh t xldx t plwl t wlrh wr rdy/bsy pagel t phpl t plbx t bvph t xlwl t wlbx t bvwl wlrl xtal1 pagel t plxh xlxh t t xlph addr0 (low byte) data (low byte) data (high byte) addr1 (low byte) data bs1 xa0 xa1 load address (low byte) load data (low byte) load data (high byte) load data load address (low byte) xtal1 oe addr0 (low byte) data (low byte) data (high byte) addr1 (low byte) data bs1 xa0 xa1 load address (low byte) read data (low byte) read data (high byte) load address (low byte) t bvdv t oldv t xlol t ohdz 205 8246b?avr?09/11 attiny2313a/4313 22.8 serial programming characteristics figure 22-6. serial programming timing note: 2 t clcl for f ck < 12 mhz, 3 t clcl for f ck >= 12 mhz figure 22-7. serial programming waveform table 22-8. serial programming characteristics, t a = -40 c to 85 c, v cc = 1.8 - 5.5v (unless otherwise noted) symbol parameter min typ max units 1/t clcl oscillator frequency (attiny2313a/4313) 0 4 mhz t clcl oscillator period (attiny2313a/4313) 250 ns 1/t clcl oscillator frequency (attiny2313a/4313, v cc = 4.5v - 5.5v) 020mhz t clcl oscillator period (attiny2313a/4313, v cc = 4.5v - 5.5v) 50 ns t shsl sck pulse width high 2 t clcl * ns t slsh sck pulse width low 2 t clcl * ns t ovsh mosi setup to sck high t clcl ns t shox mosi hold after sck high 2 t clcl ns t sliv sck low to miso valid 100 ns mosi miso sck t ovsh t shsl t slsh t shox msb msb lsb lsb serial clock input (sck) serial data input (mosi) (miso) sample serial data output 206 8246b?avr?09/11 attiny2313a/4313 23. typical characteristics the data contained in this section is largely based on simulations and characterization of similar devices in the same process and design methods. thus, the data should be treated as indica- tions of how the part will behave. the following charts show typical behavior. t hese figures are not tested during manufacturing. during characterisation devices are operated at fr equencies higher than test limits but they are not guaranteed to function properly at frequencies higher than the ordering code indicates. all current consumption measurements are performed with all i/o pins configured as inputs and with internal pull-ups enabled. current consumption is a function of several factors such as oper- ating voltage, operating frequency, loading of i/o pins, switching rate of i/o pins, code executed and ambient temperature. the dominating factors are operating voltage and frequency. a sine wave generator with rail-to-rail output is used as clock source but current consumption in power-down mode is independent of clock selection. the difference between current consump- tion in power-down mode with watchdog timer enabled and power-down mode with watchdog timer disabled represents the differential current drawn by the watchdog timer. the current drawn from pins with a capacitive lo ad may be estimated (for one pin) as follows: where v cc = operating voltage, c l = load capacitance and f sw = average switching frequency of i/o pin. 23.1 effect of power reduction peripheral modules are enabled and disabled via c ontrol bits in the power reduction register. see ?power reduction register? on page 35 for details. i cp v cc c l f sw table 23-1. additional current consumption (absolute) for peripherals of attiny2313a/4313 prr bit typical numbers v cc = 2v, f = 1mhz v cc = 3v, f = 4mhz v cc = 5v, f = 8mhz prtim0 2 a 11 a 50 a prtim1 5 a 30 a 120 a prusi 2 a 11 a 50 a prusart 4 a 22 a 95 a 207 8246b?avr?09/11 attiny2313a/4313 23.2 attiny2313a 23.2.1 current consumption in active mode figure 23-1. active supply current vs. low frequency (0.1 - 1.0 mhz) figure 23-2. active supply current vs . frequency (1 - 20 mhz) active supply current vs. low frequency (attiny2313a) (prr=0xff) 5.5 v 5.0 v 4.5 v 3.3 v 2.7 v 1.8 v 0 0,2 0,4 0,6 0,8 1 0 0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1 frequency (mhz) i cc (ma) active supply current vs. frequency (attiny2313a) (prr=0xff) 0 2 4 6 8 10 0 2 4 6 8 101214161820 frequency (mhz) i cc (ma) 1.8v 2.7v 3.3v 4.5v 5.0v 5.5v 208 8246b?avr?09/11 attiny2313a/4313 figure 23-3. active supply current vs. v cc (internal rc o scillator, 8 mhz) figure 23-4. active supply current vs. v cc (internal rc o scillator, 1 mhz) active supply current vs. v cc (attiny2313a) internal rc oscillator, 8 mhz 85 c 25 c -40 c 0 1 2 3 4 5 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) active supply current vs. v cc (attiny2313a) internal rc oscillator, 1 mhz 85 c 25 c -40 c 0 0,2 0,4 0,6 0,8 1 1,2 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) 209 8246b?avr?09/11 attiny2313a/4313 figure 23-5. active supply current vs. v cc (internal rc o scillator, 128 khz) 23.2.2 current consumption in idle mode figure 23-6. idle supply current vs. low frequency (0.1 - 1.0 mhz) active supply current vs. v cc (attiny2313a) internal rc oscillator, 128 khz 85 c 25 c -40 c 0 0,02 0,04 0,06 0,08 0,1 0,12 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) idle supply current vs. low frequency (attiny2313a) (prr=0xff) 5.5 v 5.0 v 4.5 v 4.0 v 3.3 v 2.7 v 1.8 v 0 0,02 0,04 0,06 0,08 0,1 0,12 0,14 0,16 0 0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1 frequency (mhz) i cc (ma) 210 8246b?avr?09/11 attiny2313a/4313 figure 23-7. idle supply current vs. frequency (1 - 20 mhz) figure 23-8. idle supply current vs. v cc (internal rc o scillator, 8 mhz) idle supply current vs. frequency (attiny2313a) (prr=0xff) 5.5 v 5.0 v 4.5 v 4.0 v 3.3 v 2.7 v 1.8 v 0 0,5 1 1,5 2 2,5 3 0 2 4 6 8 101214161820 frequency (mhz) i cc (ma) idle supply current vs. v cc (attiny2313a) internal rc oscillator, 8 mhz 85 c 25 c -40 c 0 0,2 0,4 0,6 0,8 1 1,2 1,4 1,6 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) 211 8246b?avr?09/11 attiny2313a/4313 figure 23-9. idle supply current vs. v cc (internal rc o scillator, 1 mhz) figure 23-10. idle supply current vs. v cc (internal rc o scillator, 128 khz) idle supply current vs. v cc (attiny2313a) internal rc oscillator, 1 mhz 85 c 25 c -40 c 0 0,05 0,1 0,15 0,2 0,25 0,3 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) idle supply current vs. v cc (attiny2313a) internal rc oscillator, 128 khz 85 c 25 c -40 c 0 0,005 0,01 0,015 0,02 0,025 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) 212 8246b?avr?09/11 attiny2313a/4313 23.2.3 current consumption in power-down mode figure 23-11. power-down supply current vs. v cc (watchdog timer disabled) figure 23-12. power-down supply current vs. v cc (watchdog timer enabled) power-down supply current vs. v cc (attiny2313a) watchdog timer disabled 85 c 25 c -40 c 0 0,1 0,2 0,3 0,4 0,5 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ua) power-down supply current vs. v cc (attiny2313a) watchdog timer enabled 85 c 25 c -40 c 0 1 2 3 4 5 6 7 8 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ua) 213 8246b?avr?09/11 attiny2313a/4313 23.2.4 current consumption in reset figure 23-13. reset supply current vs. v cc (0.1 - 1.0 mhz, excluding current through the reset pull-up) figure 23-14. reset supply current vs. v cc (1 - 20 mhz, excluding current through the reset pull-up) reset supply current vs. v cc (attiny2313a) excluding current through the reset pullup 5.5 v 5.0 v 4.5 v 4.0 v 3.3 v 2.7 v 1.8 v 0 0,02 0,04 0,06 0,08 0,1 0,12 0,14 0 0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1 frequency (mhz) i cc (ma) 5.5 v 5.0 v 4.5 v 4.0 v 3.3 v 2.7 v 1.8 v reset supply current vs. v cc (attiny2313a) excluding current through the reset pullup 0 0,2 0,4 0,6 0,8 1 1,2 1,4 1,6 1,8 2 2,2 0 2 4 6 8 101214161820 frequency (mhz) i cc (ma) 214 8246b?avr?09/11 attiny2313a/4313 23.2.5 current consumption of peripheral units figure 23-15. brownout detector current vs. v cc figure 23-16. programming current vs. v cc (attiny2313a) note: above programming current based on simulation and characterisation of similar device (attiny24a). brownout detector current vs. v cc (attiny2313a) bod level = 1.8v 85 c 25 c -40 c 0 5 10 15 20 25 30 35 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ua) programming current vs. vcc 85 c 25 c -40 c 0 1000 2000 3000 4000 5000 6000 7000 8000 9000 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ua) 215 8246b?avr?09/11 attiny2313a/4313 23.2.6 pull-up resistors figure 23-17. pull-up resistor current vs. input voltage (i/o pin, v cc = 1.8v) figure 23-18. pull-up resistor current vs. input voltage (i/o pin, v cc = 2.7v) i/o pin pull-up resistor current vs. input voltage (attiny2313a) 0 10 20 30 40 50 60 0 0,2 0,4 0,6 0,8 1 1,2 1,4 1,6 1,8 2 v op (v) i op (ua) 85 c 25 c -40 c 85 c 25 c -40 c i/o pin pull-up resistor current vs. input voltage (attiny2313a) 0 10 20 30 40 50 60 70 80 90 3 5 , 2 2 5 , 1 1 5 , 0 0 v op (v) i op (ua) 216 8246b?avr?09/11 attiny2313a/4313 figure 23-19. pull-up resistor current vs. input voltage (i/o pin, v cc = 5v) figure 23-20. reset pull-up resistor curr ent vs. reset pin voltage (v cc = 1.8v) 85 c 25 c -40 c i/o pin pull-up resistor current vs. input voltage (attiny2313a) 0 20 40 60 80 100 120 140 160 6 5 4 3 2 1 0 v op (v) i op (ua) reset pull-up resistor current vs. reset pin voltage (attiny2313a) -40 c 25 c 85 c 0 5 10 15 20 25 30 35 40 0 0,2 0,4 0,6 0,8 1 1,2 1,4 1,6 1,8 2 v reset (v) i reset (ua) 217 8246b?avr?09/11 attiny2313a/4313 figure 23-21. reset pull-up resistor curr ent vs. reset pin voltage (v cc = 2.7v) figure 23-22. reset pull-up resistor curr ent vs. reset pin voltage (v cc = 5v) -40 c 25 c 85 c reset pull-up resistor current vs. reset pin voltage (attiny2313a) 0 10 20 30 40 50 60 3 5 , 2 2 5 , 1 1 5 , 0 0 v reset (v) i reset (ua) -40 c 25 c 85 c reset pull-up resistor current vs. reset pin voltage (attiny2313a) 0 20 40 60 80 100 120 0 0,5 1 1,5 2 2,5 3 3,5 4 4,5 5 v reset (v) i reset (ua) 218 8246b?avr?09/11 attiny2313a/4313 23.2.7 output driver strength figure 23-23. v ol : output voltage vs. sink current (i/o pin, v cc = 1.8v) figure 23-24. v ol : output voltage vs. sink current (i/o pin, v cc = 3v) i/o pin output voltage vs. sink current (attiny2313a) vcc = 1.8v 85 c 25 c -40 c 0 0,05 0,1 0,15 0,2 0,25 0,3 0,35 0,4 0 0,5 1 1,5 2 2,5 3 3,5 4 4,5 5 i ol (ma) v ol (v) i/o pin output voltage vs. sink current (attiny2313a) vcc = 3v 85 c 25 c -40 c 0 0,2 0,4 0,6 0 1 8 6 4 2 0 i ol (ma) v ol (v) 219 8246b?avr?09/11 attiny2313a/4313 figure 23-25. v ol : output voltage vs. sink current (i/o pin, v cc = 5v) figure 23-26. v oh : output voltage vs. source current (i/o pin, v cc = 1.8v) i/o pin output voltage vs. sink current (attiny2313a) vcc = 5v 85 c 25 c -40 c 0 0,1 0,2 0,3 0,4 0,5 0,6 0 2 4 6 8 101214161820 i ol (ma) v ol (v) i/o pin output voltage vs. source current (attiny2313a) vcc = 1.8v 85 c 25 c -40 c 1,2 1,3 1,4 1,5 1,6 1,7 1,8 1,9 0 0,5 1 1,5 2 2,5 3 3,5 4 4,5 5 i oh (ma) v oh (v) 220 8246b?avr?09/11 attiny2313a/4313 figure 23-27. v oh : output voltage vs. source current (i/o pin, v cc = 3v) figure 23-28. v oh : output voltage vs. source current (i/o pin, v cc = 5v) i/o pin output voltage vs. source current (attiny2313a) vcc = 3v 85 c 25 c -40 c 2,5 2,6 2,7 2,8 2,9 3 3,1 0 1 8 6 4 2 0 i oh (ma) v oh (v) i/o pin output voltage vs. source current (attiny2313a) vcc = 5v 85 c 25 c -40 c 4,3 4,5 4,7 4,9 5,1 0 2 5 1 0 1 5 0 i oh (ma) v oh (v) 221 8246b?avr?09/11 attiny2313a/4313 figure 23-29. v ol : output voltage vs. sink current (reset pin as i/o, t = 25c) figure 23-30. v oh : output voltage vs. source current (reset pin as i/o, t = 25c) reset as i/o pin output voltage vs. sink current (attiny2313a) 0 0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1 4 3 2 1 0 i ol (ma) v ol (v) 5.0 v 3.0 v 1.8 v reset as i/o pin output voltage vs. source current (attiny2313a) 5.0 v 3.0 v 1.8 v 0 1 2 3 4 5 1 8 , 0 6 , 0 4 , 0 2 , 0 0 i oh (ma) v oh (v) 222 8246b?avr?09/11 attiny2313a/4313 23.2.8 input thresholds and hysteresis (for i/o ports) figure 23-31. v ih : input threshold voltage vs. v cc (i/o pin read as ?1?) figure 23-32. v il : input threshold voltage vs. v cc (i/o pin, read as ?0?) i/o pin input threshold voltage vs. v cc (attiny2313a) vih, io pin read as '1' 0 0,5 1 1,5 2 2,5 3 3,5 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) threshold (v) 85 c 25 c -40 c i/o pin input threshold voltage vs. v cc (attiny2313a) vil, io pin read as '0' 0 0,5 1 1,5 2 2,5 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) threshold (v) 85 c 25 c -40 c 223 8246b?avr?09/11 attiny2313a/4313 figure 23-33. v ih -v il : input hysteresis vs. v cc (i/o pin) figure 23-34. v ih : input threshold voltage vs. v cc (reset pin as i/o, read as ?1?) i/o pin input hysteresis vs. v cc (attiny2313a) 85 c 25 c -40 c 0 0,1 0,2 0,3 0,4 0,5 0,6 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) input hysteresis (v) reset pin as i/o threshold voltage vs. v cc (attiny2313a) vih, reset read as '1' 85 c 25 c -40 c 0 0,5 1 1,5 2 2,5 3 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) threshold (v) 224 8246b?avr?09/11 attiny2313a/4313 figure 23-35. v il : input threshold voltage vs. v cc (reset pin as i/o, read as ?0?) figure 23-36. v ih -v il : input hysteresis vs. v cc (reset pin as i/o) reset pin as i/o threshold voltage vs. v cc (attiny2313a) vil, reset read as '0' 0 0,5 1 1,5 2 2,5 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) threshold (v) 85 c 25 c -40 c reset pin as io, input hysteresis vs. v cc (attiny2313a) vil, io pin read as "0" 85 c 25 c -40 c 0 0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) input hysteresis (v) 225 8246b?avr?09/11 attiny2313a/4313 23.2.9 bod, bandgap and reset figure 23-37. bod thresholds vs. temperature (bod level is 4.3v) figure 23-38. bod thresholds vs. temperature (bod level is 2.7v) bod thresholds vs. temperature (bod level set to 4.3v) (attiny2313a) bodlevel = 4.3v 4,22 4,24 4,26 4,28 4,3 4,32 4,34 4,36 -40 -30 -20 -10 0 10 20 30 40 50 60 70 80 90 100 temperature (c) threshold (v) v cc rising v cc falling bod thresholds vs. temperature (bod level set to 2.7v) (attiny2313a) bodlevel = 2.7v 2,66 2,68 2,7 2,72 2,74 2,76 2,78 -40 -20 0 20 40 60 80 100 temperature (c) threshold (v) v cc rising v cc falling 226 8246b?avr?09/11 attiny2313a/4313 figure 23-39. bod thresholds vs. temperature (bod level is 1.8v) figure 23-40. bandgap voltage vs. supply voltage bod thresholds vs. temperature (bod level set to 1.8v) (attiny2313a) bodlevel = 1.8v 1,78 1,79 1,8 1,81 1,82 1,83 1,84 -40 -20 0 20 40 60 80 100 temperature (c) threshold (v) v cc rising v cc falling bandgap voltage vs. v cc (attiny2313a) calibrated 0,95 1 1,05 1,1 1,15 1,2 1,5 2 2,5 3 3,5 4 4,5 5 5,5 vcc (v) bandgap voltage (v) 227 8246b?avr?09/11 attiny2313a/4313 figure 23-41. bandgap voltage vs. temperature figure 23-42. v ih : input threshold voltage vs. v cc (reset pin, read as ?1?) bandgap voltage vs. temp (attiny2313a) (vcc=5v) calibrated 1 1,02 1,04 1,06 1,08 1,1 1,12 1,14 1,16 -40 -20 0 20 40 60 80 100 temperature bandgap voltage (v) reset input threshold voltage vs. v cc (attiny2313a) vih, io pin read as '1' 85 c 25 c -40 c 0 0,5 1 1,5 2 2,5 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) threshold (v) 228 8246b?avr?09/11 attiny2313a/4313 figure 23-43. v il : input threshold voltage vs. v cc (reset pin, read as ?0?) figure 23-44. v ih -v il : input hysteresis vs. v cc (reset pin) reset input threshold voltage vs. v cc (attiny2313a) vil, io pin read as '0' 85 c 25 c -40 c 0 0,5 1 1,5 2 2,5 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) threshold (v) reset pin input hysteresis vs. v cc (attiny2313a) 0 0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) input hysteresis (v) 85 c 25 c -40 c 229 8246b?avr?09/11 attiny2313a/4313 figure 23-45. minimum reset pulse width vs. v cc 23.2.10 internal oscillator speed figure 23-46. calibrated 8 mhz rc osc illator frequency vs. v cc minimum reset pulse width vs. v cc (attiny2313a) 85 c 25 c -40 c 0 200 400 600 800 1000 1200 1400 1600 1800 2000 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) pulsewidth (ns) calibrated 8.0mhz rc oscillator frequency vs. operating voltage (attiny2313a) 7 7,2 7,4 7,6 7,8 8 8,2 8,4 8,6 8,8 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) f rc (mhz) 85 c 25 c -40 c 230 8246b?avr?09/11 attiny2313a/4313 figure 23-47. calibrated 8 mhz rc oscillato r frequency vs. temperature figure 23-48. calibrated 8 mhz rc oscillato r frequency vs. osccal value calibrated 8.0mhz rc oscillator frequency vs. temperature (attiny2313a) 5.0 v 3.0 v 1.8 v 7 7,5 8 8,5 9 -40 -20 0 20 40 60 80 100 temperature f rc (mhz) calibrated 8.0mhz rc oscillator frequency vs. osccal value (attiny2313a) (vcc=3v) 85 c 25 c -40 c 0 2 4 6 8 10 12 14 0 163248648096112 osccal (x1) f rc (mhz) 231 8246b?avr?09/11 attiny2313a/4313 23.3 attiny4313 23.3.1 current consumption in active mode figure 23-49. active supply current vs. low frequency (0.1 - 1.0 mhz) figure 23-50. active supply current vs . frequency (1 - 20 mhz) active supply current vs. low frequency (attiny4313) (prr=0xff) 5.5 v 5.0 v 4.5 v 3.3 v 2.7 v 1.8 v 0 0,2 0,4 0,6 0,8 1 0 0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1 frequency (mhz) i cc (ma) active supply current vs. frequency (attiny4313) (prr=0xff) 0 2 4 6 8 10 02468101214161820 frequency (mhz) i cc (ma) 1.8v 2.7v 3.3v 4.5v 5.0v 5.5v 232 8246b?avr?09/11 attiny2313a/4313 figure 23-51. active supply current vs. v cc (internal rc o scillator, 8 mhz) figure 23-52. active supply current vs. v cc (internal rc o scillator, 1 mhz) active supply current vs. v cc (attiny4313) internal rc oscillator, 8 mhz 85 c 25 c -40 c 0 1 2 3 4 5 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) active supply current vs. v cc (attiny4313) internal rc oscillator, 1 mhz 85 c 25 c -40 c 0 0,2 0,4 0,6 0,8 1 1,2 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) 233 8246b?avr?09/11 attiny2313a/4313 figure 23-53. active supply current vs. v cc (internal rc o scillator, 128 khz) 23.3.2 current consumption in idle mode figure 23-54. idle supply current vs. low frequency (0.1 - 1.0 mhz) active supply current vs. v cc (attiny4313) internal rc oscillator, 128 khz 85 c 25 c -40 c 0 0,02 0,04 0,06 0,08 0,1 0,12 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) idle supply current vs. low frequency (attiny4313) (prr=0xff) 5.5 v 5.0 v 4.5 v 4.0 v 3.3 v 2.7 v 1.8 v 0 0,02 0,04 0,06 0,08 0,1 0,12 0,14 0,16 0 0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1 frequency (mhz) i cc (ma) 234 8246b?avr?09/11 attiny2313a/4313 figure 23-55. idle supply current vs. frequency (1 - 20 mhz) figure 23-56. idle supply current vs. v cc (internal rc o scillator, 8 mhz) idle supply current vs. frequency (attiny4313) (prr=0xff) 0 0,5 1 1,5 2 2,5 3 0 2 4 6 8 101214161820 frequency (mhz) i cc (ma) 5.5 v 5.0 v 4.5 v 4.0 v 3.3 v 2.7 v 1.8 v idle supply current vs. v cc (attiny4313) internal rc oscillator, 8 mhz 85 c 25 c -40 c 0 0,2 0,4 0,6 0,8 1 1,2 1,4 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) 235 8246b?avr?09/11 attiny2313a/4313 figure 23-57. idle supply current vs. v cc (internal rc o scillator, 1 mhz) figure 23-58. idle supply current vs. v cc (internal rc o scillator, 128 khz) idle supply current vs. v cc (attiny4313) internal rc oscillator, 1 mhz 85 c 25 c -40 c 0 0,1 0,2 0,3 0,4 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) idle supply current vs. v cc (attiny4313) internal rc oscillator, 128 khz 85 c 25 c -40 c 0 0,005 0,01 0,015 0,02 0,025 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) 236 8246b?avr?09/11 attiny2313a/4313 23.3.3 current consumption in power-down mode figure 23-59. power-down supply current vs. v cc (watchdog timer disabled) figure 23-60. power-down supply current vs. v cc (watchdog timer enabled) power-down supply current vs. v cc (attiny4313) watchdog timer disabled 85 c 25 c -40 c 0 0,1 0,2 0,3 0,4 0,5 0,6 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ua) power-down supply current vs. v cc (attiny4313) watchdog timer enabled 85 c 25 c -40 c 0 1 2 3 4 5 6 7 8 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ua) 237 8246b?avr?09/11 attiny2313a/4313 23.3.4 current consumption in reset figure 23-61. reset supply current vs. v cc (0.1 - 1.0 mhz, excluding current through the reset pull-up) figure 23-62. reset supply current vs. v cc (1 - 20 mhz, excluding current through the reset pull-up) reset supply current vs. v cc (attiny4313) excluding current through the reset pullup 5.5 v 5.0 v 4.5 v 4.0 v 3.3 v 2.7 v 1.8 v 0 0,02 0,04 0,06 0,08 0,1 0,12 0 0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1 frequency (mhz) i cc (ma) reset supply current vs. v cc (attiny4313) excluding current through the reset pullup 0 0,2 0,4 0,6 0,8 1 1,2 1,4 1,6 1,8 2 2,2 0 2 4 6 8 10 12 14 16 18 20 frequency (mhz) i cc (ma) 5.5 v 5.0 v 4.5 v 4.0 v 3.3 v 2.7 v 1.8 v 238 8246b?avr?09/11 attiny2313a/4313 23.3.5 current consumption of peripheral units figure 23-63. brownout detector current vs. v cc figure 23-64. programming current vs. v cc (attiny4313) note: above programming current based on simulation and characterisation of similar device (attiny44a). brownout detector current vs. v cc (attiny4313) bod level = 1.8v 85 c 25 c -40 c 0 5 10 15 20 25 30 35 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ua) programming current vs. vcc 85 c 25 c -40 c 0 2000 4000 6000 8000 10000 12000 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ua) 239 8246b?avr?09/11 attiny2313a/4313 23.3.6 pull-up resistors figure 23-65. pull-up resistor current vs. input voltage (i/o pin, v cc = 1.8v) figure 23-66. pull-up resistor current vs. input voltage (i/o pin, v cc = 2.7v) i/o pin pull-up resistor current vs. input voltage (attiny4313) 0 10 20 30 40 50 60 0 0,2 0,4 0,6 0,8 1 1,2 1,4 1,6 1,8 2 v op (v) i op (ua) 85 c 25 c -40 c i/o pin pull-up resistor current vs. input voltage (attiny4313) 0 10 20 30 40 50 60 70 80 3 5 , 2 2 5 , 1 1 5 , 0 0 v op (v) i op (ua) 85 c 25 c -40 c 240 8246b?avr?09/11 attiny2313a/4313 figure 23-67. pull-up resistor current vs. input voltage (i/o pin, v cc = 5v) figure 23-68. reset pull-up resistor curr ent vs. reset pin voltage (v cc = 1.8v) i/o pin pull-up resistor current vs. input voltage (attiny4313) 0 20 40 60 80 100 120 140 160 6 5 4 3 2 1 0 v op (v) i op (ua) 85 c 25 c -40 c reset pull-up resistor current vs. reset pin voltage (attiny4313) 0 5 10 15 20 25 30 35 40 0 0,2 0,4 0,6 0,8 1 1,2 1,4 1,6 1,8 2 v reset (v) i reset (ua) 85 c 25 c -40 c 241 8246b?avr?09/11 attiny2313a/4313 figure 23-69. reset pull-up resistor curr ent vs. reset pin voltage (v cc = 2.7v) figure 23-70. reset pull-up resistor curr ent vs. reset pin voltage (v cc = 5v) reset pull-up resistor current vs. reset pin voltage (attiny4313) 0 10 20 30 40 50 60 3 5 , 2 2 5 , 1 1 5 , 0 0 v reset (v) i reset (ua) 85 c 25 c -40 c reset pull-up resistor current vs. reset pin voltage (attiny4313) 0 20 40 60 80 100 120 6 5 4 3 2 1 0 v reset (v) i reset (ua) 242 8246b?avr?09/11 attiny2313a/4313 23.3.7 output driver strength figure 23-71. v ol : output voltage vs. sink current (i/o pin, v cc = 1.8v) figure 23-72. v ol : output voltage vs. sink current (i/o pin, v cc = 3v) i/o pin output voltage vs. sink current (attiny4313) 0 0,05 0,1 0,15 0,2 0,25 0,3 0,35 0,4 0 0,5 1 1,5 2 2,5 3 3,5 4 4,5 5 i ol (ma) v ol (v) v cc = 1.8v 85 c 25 c -40 c i/o pin output voltage vs. sink current (attiny4313) 0 0,1 0,2 0,3 0,4 0,5 0,6 0 1 8 6 4 2 0 i ol (ma) v ol (v) v cc = 3v 85 c 25 c -40 c 243 8246b?avr?09/11 attiny2313a/4313 figure 23-73. v ol : output voltage vs. sink current (i/o pin, v cc = 5v) figure 23-74. v oh : output voltage vs. source current (i/o pin, v cc = 1.8v) i/o pin output voltage vs. sink current (attiny4313) 85 c 25 c -40 c 0 0,1 0,2 0,3 0,4 0,5 0,6 0 2 4 6 8 101214161820 i ol (ma) v ol (v) v cc = 5v i/o pin output voltage vs. source current (attiny4313) 1 1,2 1,4 1,6 1,8 2 0 0,5 1 1,5 2 2,5 3 3,5 4 4,5 5 i oh (ma) v oh (v) v cc = 1.8v 85 c 25 c -40 c 244 8246b?avr?09/11 attiny2313a/4313 figure 23-75. v oh : output voltage vs. source current (i/o pin, v cc = 3v) figure 23-76. v oh : output voltage vs. source current (i/o pin, v cc = 5v) i/o pin output voltage vs. source current (attiny4313) 2,5 2,6 2,7 2,8 2,9 3 3,1 0 1 8 6 4 2 0 i oh (ma) v oh (v) v cc = 3v 85 c 25 c -40 c i/o pin output voltage vs. source current (attiny4313) 85 c 25 c -40 c 4,3 4,5 4,7 4,9 5,1 0 2 5 1 0 1 5 0 i oh (ma) v oh (v) v cc = 5v 245 8246b?avr?09/11 attiny2313a/4313 figure 23-77. v ol : output voltage vs. sink current (reset pin as i/o, t = 25c) figure 23-78. v oh : output voltage vs. source current (reset pin as i/o, t = 25c) reset as i/o pin output voltage vs. sink current (attiny4313) 0 0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1 4 3 2 1 0 i ol (ma) v ol (v) 5.0 v 3.0 v 1.8 v reset as i/o pin output voltage vs. source current (attiny4313) 0 1 2 3 4 5 1 8 , 0 6 , 0 4 , 0 2 , 0 0 i oh (ma) v oh (v) 5.0v 3.0v 1.8v 246 8246b?avr?09/11 attiny2313a/4313 23.3.8 input thresholds and hysteresis (for i/o ports) figure 23-79. v ih : input threshold voltage vs. v cc (i/o pin read as ?1?) figure 23-80. v il : input threshold voltage vs. v cc (i/o pin, read as ?0?) i/o pin input threshold voltage vs. v cc (attiny4313) vih, io pin read as '1' 85 c 25 c -40 c 0 0,5 1 1,5 2 2,5 3 3,5 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) threshold (v) i/o pin input threshold voltage vs. v cc (attiny4313) vil, io pin read as '0' 85 c 25 c -40 c 0 0,5 1 1,5 2 2,5 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) threshold (v) 247 8246b?avr?09/11 attiny2313a/4313 figure 23-81. v ih -v il : input hysteresis vs. v cc (i/o pin) figure 23-82. v ih : input threshold voltage vs. v cc (reset pin as i/o, read as ?1?) i/o pin input hysteresis vs. v cc (attiny4313) 85 c 25 c -40 c 0 0,1 0,2 0,3 0,4 0,5 0,6 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) input hysteresis (v) reset pin as i/o threshold voltage vs. v cc (attiny4313) vih, reset read as '1' 85 c 25 c -40 c 0 0,5 1 1,5 2 2,5 3 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) threshold (v) 248 8246b?avr?09/11 attiny2313a/4313 figure 23-83. v il : input threshold voltage vs. v cc (reset pin as i/o, read as ?0?) figure 23-84. v ih -v il : input hysteresis vs. v cc (reset pin as i/o) reset pin as i/o threshold voltage vs. v cc (attiny4313) vil, reset read as '0' 85 c 25 c -40 c 0 0,5 1 1,5 2 2,5 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) threshold (v) reset pin as io, input hysteresis vs. v cc (attiny4313) vil, io pin read as "0" 85 c 25 c -40 c 0 0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) input hysteresis (v) 249 8246b?avr?09/11 attiny2313a/4313 23.3.9 bod, bandgap and reset figure 23-85. bod thresholds vs. temperature (bod level is 4.3v) figure 23-86. bod thresholds vs. temperature (bod level is 2.7v) bod thresholds vs. temperature (bod level set to 4.3v) (attiny4313) bod level = 4.3v 4,16 4,18 4,2 4,22 4,24 4,26 4,28 4,3 4,32 4,34 4,36 4,38 -40 -30 -20 -10 0 10 20 30 40 50 60 70 80 90 100 temperature (c) threshold (v) v cc rising v cc falling bod thresholds vs. temperature (bod level set to 2.7v) (attiny4313) bod level = 2.7v 2,62 2,64 2,66 2,68 2,7 2,72 2,74 2,76 2,78 -40 -20 0 20 40 60 80 100 temperature (c) threshold (v) v cc rising v cc falling 250 8246b?avr?09/11 attiny2313a/4313 figure 23-87. bod thresholds vs. temperature (bod level is 1.8v) figure 23-88. bandgap voltage vs. supply voltage 1,76 1,77 1,78 1,79 1,8 1,81 1,82 1,83 1,84 -40 -20 0 20 40 60 80 100 temperature (c) threshold (v) bod thresholds vs. temperature (bod level set to 1.8v) (attiny4313) bod level = 1.8v v cc rising v cc falling bandgap voltage vs. v cc (attiny4313) calibrated 0,95 1 1,05 1,1 1,15 1,2 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) bandgap voltage (v) 251 8246b?avr?09/11 attiny2313a/4313 figure 23-89. bandgap voltage vs. temperature figure 23-90. v ih : input threshold voltage vs. v cc (reset pin, read as ?1?) bandgap voltage vs. temp (attiny4313) (vcc=5v) calibrated 1 1,02 1,04 1,06 1,08 1,1 1,12 1,14 -40 -20 0 20 40 60 80 100 temperature bandgap voltage (v) reset input threshold voltage vs. v cc (attiny4313) vih, io pin read as '1' 85 c 25 c -40 c 0 0,5 1 1,5 2 2,5 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) threshold (v) 252 8246b?avr?09/11 attiny2313a/4313 figure 23-91. v il : input threshold voltage vs. v cc (reset pin, read as ?0?) figure 23-92. v ih -v il : input hysteresis vs. v cc (reset pin) reset input threshold voltage vs. v cc (attiny4313) vil, io pin read as '0' 85 c 25 c -40 c 0 0,5 1 1,5 2 2,5 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) threshold (v) reset pin input hysteresis vs. v cc (attiny4313) 85 c 25 c -40 c 0 0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) input hysteresis (v) 253 8246b?avr?09/11 attiny2313a/4313 figure 23-93. minimum reset pulse width vs. v cc 23.3.10 internal oscillator speed figure 23-94. calibrated 8 mhz rc osc illator frequency vs. v cc minimum reset pulse width vs. v cc (attiny4313) 85 c 25 c -40 c 0 200 400 600 800 1000 1200 1400 1600 1800 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) pulsewidth (ns) calibrated 8.0mhz rc oscillator frequency vs. operating voltage (attiny4313) 7,2 7,4 7,6 7,8 8 8,2 8,4 8,6 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) f rc (mhz) 85 c 25 c -40 c 254 8246b?avr?09/11 attiny2313a/4313 figure 23-95. calibrated 8 mhz rc oscillato r frequency vs. temperature figure 23-96. calibrated 8 mhz rc oscillato r frequency vs. osccal value calibrated 8.0mhz rc oscillator frequency vs. temperature (attiny4313) 5.0 v 3.0 v 1.8 v 7,4 7,6 7,8 8 8,2 8,4 8,6 -40 -20 0 20 40 60 80 100 temperature f rc (mhz) calibrated 8.0mhz rc oscillator frequency vs. osccal value (attiny4313) (vcc=3v) 85 c 25 c -40 c 0 2 4 6 8 10 12 14 0 163248648096112 osccal (x1) f rc (mhz) 255 8246b?avr?09/11 attiny2313a/4313 24. register summary address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 page 0x3f (0x5f) sreg i t h s v n z c 9 0x3e (0x5e) reserved ? ? ? ? ? ? ? ? 0x3d (0x5d) spl sp7 sp6 sp5 sp4 sp3 sp2 sp1 sp0 12 0x3c (0x5c) ocr0b timer/counter0 ? compare register b 86 0x3b (0x5b) gimsk int1 int0 pcie0 pcie2 pcie1 ? ? ?52 0x3a (0x5a) gifr intf1 intf0 pcif0 pcif2 pcif1 ? ? ?53 0x39 (0x59) timsk toie1 ocie1a ocie1b ? icie1 ocie0b toie0 ocie0a 87, 116 0x38 (0x58) tifr tov1 ocf1a ocf1b ? icf1 ocf0b tov0 ocf0a 87, 117 0x37 (0x57) spmcsr ? ? rsig ctpb rflb pgwrt pgers spmen 176 0x36 (0x56) ocr0a timer/counter0 ? compare register a 86 0x35 (0x55) mcucr pud sm1 se sm0 isc11 isc10 isc01 isc00 37, 51, 69 0x34 (0x54) mcusr ? ? ? ? wdrf borf extrf porf 45 0x33 (0x53) tccr0b foc0a foc0b ? ? wgm02 cs02 cs01 cs00 85 0x32 (0x52) tcnt0 timer/counter0 (8-bit) 86 0x31 (0x51) osccal ? cal6 cal5 cal4 cal3 cal2 cal1 cal0 32 0x30 (0x50) tccr0a com0a1 com0a0 com0b1 com0b0 ? ?wgm01wgm00 82 0x2f (0x4f) tccr1a com1a1 com1a0 com1b1 com1b0 ? ? wgm11 wgm10 111 0x2e (0x4e) tccr1b icnc1 ices1 ? wgm13 wgm12 cs12 cs11 cs10 113 0x2d (0x4d) tcnt1h timer/counter1 ? counter register high byte 115 0x2c (0x4c) tcnt1l timer/counter1 ? counter register low byte 115 0x2b (0x4b) ocr1ah timer/counter1 ? compare register a high byte 115 0x2a (0x4a) ocr1al timer/counter1 ? compare register a low byte 115 0x29 (0x49) ocr1bh timer/counter1 ? compare register b high byte 115 0x28 (0x48) ocr1bl timer/counter1 ? compare register b low byte 115 0x27 (0x47) reserved ? ? ? ? ? ? ? ? 0x26 (0x46) clkpr clkpce ? ? ? clkps3 clkps2 clkps1 clkps0 32 0x25 (0x45) icr1h timer/counter1 - input capture register high byte 116 0x24 (0x44) icr1l timer/counter1 - input capture register low byte 116 0x23 (0x43) gtccr ? ? ? ? ? ? ? psr10 119 0x22 (ox42) tccr1c foc1a foc1b ? ? ? ? ? ? 114 0x21 (0x41) wdtcsr wdif wdie wdp3 wdce wde wdp2 wdp1 wdp0 45 0x20 (0x40) pcmsk0 pcint7 pcint6 pcint5 pcint4 pcint3 pcint2 pcint1 pcint0 54 0x1f (0x3f) reserved ? ? ? ? ? ? ? ? 0x1e (0x3e) eear ? eeprom address register 24 0x1d (0x3d) eedr eeprom data register 23 0x1c (0x3c) eecr ? ? eepm1 eepm0 eerie eempe eepe eere 24 0x1b (0x3b) porta ? ? ? ? ? porta2 porta1 porta0 69 0x1a (0x3a) ddra ? ? ? ? ? dda2 dda1 dda0 69 0x19 (0x39) pina ? ? ? ? ? pina2 pina1 pina0 70 0x18 (0x38) portb portb7 portb6 portb 5 portb4 portb3 portb2 portb1 portb0 70 0x17 (0x37) ddrb ddb7 ddb6 ddb 5 ddb4 ddb3 ddb2 ddb1 ddb0 70 0x16 (0x36) pinb pinb7 pinb6 pinb5 pinb4 pinb3 pinb2 pinb1 pinb0 70 0x15 (0x35) gpior2 general purpose i/o register 2 25 0x14 (0x34) gpior1 general purpose i/o register 1 25 0x13 (0x33) gpior0 general purpose i/o register 0 25 0x12 (0x32) portd ? portd6 portd5 portd4 portd3 portd2 portd1 portd0 70 0x11 (0x31) ddrd ? ddd6 ddd5 ddd4 ddd3 ddd2 ddd1 ddd0 70 0x10 (0x30) pind ? pind6 pind5 pind4 pind3 pind2 pind1 pind0 70 0x0f (0x2f) usidr usi data register 166 0x0e (0x2e) usisr usisif usioif usipf usidc usicnt3 usicnt2 usicnt1 usicnt0 165 0x0d (0x2d) usicr usisie usioie usiwm1 usiwm0 usics1 usics0 usiclk usitc 163 0x0c (0x2c) udr uart data register (8-bit) 137 0x0b (0x2b) ucsra rxc txc udre fe dor upe u2x mpcm 138 0x0a (0x2a) ucsrb rxcie txcie udrie rxen txen ucsz2 rxb8 txb8 139 0x09 (0x29) ubrrl ubrrh[7:0] 141 0x08 (0x28) acsr acd acbg aco aci acie acic acis1 acis0 168 0x07 (0x27) bodcr ? ? ? ? ? ?bodsbodse 38 0x06 (0x26) prr ? ? ? ? prtim1 prtim0 prusi prusart 37 0x05 (0x25) pcmsk2 ? pcint17 pcint16 pcint15 pcint14 pcint13 pcint12 pcint11 53 0x04 (0x24) pcmsk1 ? ? ? ? ? pcint10 pcint9 pcint8 54 0x03 (0x23) ucsrc umsel1 umsel 0 upm1 upm0 usbs ucsz1 ucsz0 ucpol 140 0x02 (0x22) ubrrh ? ? ? ? ubrrh[11:8] 141 0x01 (0x21) didr ? ? ? ? ? ? ain1d ain0d 169 0x00 (0x20) usibr usi buffer register 167 256 8246b?avr?09/11 attiny2313a/4313 notes: 1. for compatibility with future devices, reserved bits s hould be written to zero if accessed. reserved i/o memory address es should never be written. 2. i/o registers within the address range 0x00 - 0x1f are directly bit-accessible using the sbi and cbi instructions. in these registers, the value of single bits can be ch ecked by using the sbis and sbic instructions. 3. some of the status flags are cleared by writing a logical o ne to them. note that, unlike most other avrs, the cbi and sbi instructions will only operate on the specif ied bit, and can therefore be used on regi sters containing such status flags. the cbi and sbi instructions work wit h registers 0x00 to 0x1f only. 4. when using the i/o specific commands in and out, the i/o addresses 0x00 - 0x3f must be used. when addressing i/o registers as data space using ld and st instru ctions, 0x20 must be added to these addresses. 257 8246b?avr?09/11 attiny2313a/4313 25. instruction set summary mnemonics operands description operation flags #clocks arithmetic and logic instructions add rd, rr add two registers rd rd + rr z,c,n,v,h 1 adc rd, rr add with carry two registers rd rd + rr + c z,c,n,v,h 1 adiw rdl,k add immediate to word rdh:rdl rdh:rdl + k z,c,n,v,s 2 sub rd, rr subtract two registers rd rd - rr z,c,n,v,h 1 subi rd, k subtract constant from register rd rd - k z,c,n,v,h 1 sbc rd, rr subtract with carry two registers rd rd - rr - c z,c,n,v,h 1 sbci rd, k subtract with carry constant from reg. rd rd - k - c z,c,n,v,h 1 sbiw rdl,k subtract immediate from word rdh:rdl rdh:rdl - k z,c,n,v,s 2 and rd, rr logical and registers rd rd ? rr z,n,v 1 andi rd, k logical and register and constant rd rd ? k z,n,v 1 or rd, rr logical or registers rd rd v rr z,n,v 1 ori rd, k logical or register and constant rd rd v k z,n,v 1 eor rd, rr exclusive or registers rd rd rr z,n,v 1 com rd one?s complement rd 0xff ? rd z,c,n,v 1 neg rd two?s complement rd 0x00 ? rd z,c,n,v,h 1 sbr rd,k set bit(s) in register rd rd v k z,n,v 1 cbr rd,k clear bit(s) in register rd rd ? (0xff - k) z,n,v 1 inc rd increment rd rd + 1 z,n,v 1 dec rd decrement rd rd ? 1 z,n,v 1 tst rd test for zero or minus rd rd ? rd z,n,v 1 clr rd clear register rd rd rd z,n,v 1 ser rd set register rd 0xff none 1 branch instructions rjmp k relative jump pc pc + k + 1 none 2 ijmp indirect jump to (z) pc z none 2 rcall k relative subroutine call pc pc + k + 1 none 3 icall indirect call to (z) pc znone3 ret subroutine return pc stack none 4 reti interrupt return pc stack i 4 cpse rd,rr compare, skip if equal if (rd = rr) pc pc + 2 or 3 none 1/2/3 cp rd,rr compare rd ? rr z, n,v,c,h 1 cpc rd,rr compare with carry rd ? rr ? c z, n,v,c,h 1 cpi rd,k compare register with immediate rd ? k z, n,v,c,h 1 sbrc rr, b skip if bit in register cleared if (rr(b)=0) pc pc + 2 or 3 none 1/2/3 sbrs rr, b skip if bit in register is set if (rr(b)=1) pc pc + 2 or 3 none 1/2/3 sbic p, b skip if bit in i/o register cleared if (p(b)=0) pc pc + 2 or 3 none 1/2/3 sbis p, b skip if bit in i/o register is set if (p(b)=1) pc pc + 2 or 3 none 1/2/3 brbs s, k branch if status flag set if (sreg(s) = 1) then pc pc+k + 1 none 1/2 brbc s, k branch if status flag cleared if (sreg(s) = 0) then pc pc+k + 1 none 1/2 breq k branch if equal if (z = 1) then pc pc + k + 1 none 1/2 brne k branch if not equal if (z = 0) then pc pc + k + 1 none 1/2 brcs k branch if carry set if (c = 1) then pc pc + k + 1 none 1/2 brcc k branch if carry cleared if (c = 0) then pc pc + k + 1 none 1/2 brsh k branch if same or higher if (c = 0) then pc pc + k + 1 none 1/2 brlo k branch if lower if (c = 1) then pc pc + k + 1 none 1/2 brmi k branch if minus if (n = 1) then pc pc + k + 1 none 1/2 brpl k branch if plus if (n = 0) then pc pc + k + 1 none 1/2 brge k branch if greater or equal, signed if (n v= 0) then pc pc + k + 1 none 1/2 brlt k branch if less than zero, signed if (n v= 1) then pc pc + k + 1 none 1/2 brhs k branch if half carry flag set if (h = 1) then pc pc + k + 1 none 1/2 brhc k branch if half carry flag cleared if (h = 0) then pc pc + k + 1 none 1/2 brts k branch if t flag set if (t = 1) then pc pc + k + 1 none 1/2 brtc k branch if t flag cleared if (t = 0) then pc pc + k + 1 none 1/2 brvs k branch if overflow flag is set if (v = 1) then pc pc + k + 1 none 1/2 brvc k branch if overflow flag is cleared if (v = 0) then pc pc + k + 1 none 1/2 brie k branch if interrupt enabled if ( i = 1) then pc pc + k + 1 none 1/2 brid k branch if interrupt disabled if ( i = 0) then pc pc + k + 1 none 1/2 bit and bit-test instructions sbi p,b set bit in i/o register i/o(p,b) 1none2 cbi p,b clear bit in i/o register i/o(p,b) 0none2 lsl rd logical shift left rd(n+1) rd(n), rd(0) 0 z,c,n,v 1 lsr rd logical shift right rd(n) rd(n+1), rd(7) 0 z,c,n,v 1 rol rd rotate left through carry rd(0) c,rd(n+1) rd(n),c rd(7) z,c,n,v 1 258 8246b?avr?09/11 attiny2313a/4313 ror rd rotate right through carry rd(7) c,rd(n) rd(n+1),c rd(0) z,c,n,v 1 asr rd arithmetic shift right rd(n) rd(n+1), n=0..6 z,c,n,v 1 swap rd swap nibbles rd(3..0) rd(7..4),rd(7..4) rd(3..0) none 1 bset s flag set sreg(s) 1 sreg(s) 1 bclr s flag clear sreg(s) 0 sreg(s) 1 bst rr, b bit store from register to t t rr(b) t 1 bld rd, b bit load from t to register rd(b) tnone1 sec set carry c 1c1 clc clear carry c 0 c 1 sen set negative flag n 1n1 cln clear negative flag n 0 n 1 sez set zero flag z 1z1 clz clear ze ro flag z 0 z 1 sei global interrupt enable i 1i1 cli global interrupt disable i 0 i 1 ses set signed test flag s 1s1 cls clear signed test flag s 0 s 1 sev set twos complement overflow. v 1v1 clv clear twos complement overflow v 0 v 1 set set t in sreg t 1t1 clt clear t in sreg t 0 t 1 seh set half carry flag in sreg h 1h1 clh clear half carry flag in sreg h 0 h 1 data transfer instructions mov rd, rr move between registers rd rr none 1 movw rd, rr copy register word rd+1:rd rr+1:rr none 1 ldi rd, k load immediate rd knone1 ld rd, x load indirect rd (x) none 2 ld rd, x+ load indirect and post-inc. rd (x), x x + 1 none 2 ld rd, - x load indirect and pre-dec. x x - 1, rd (x) none 2 ld rd, y load indirect rd (y) none 2 ld rd, y+ load indirect and post-inc. rd (y), y y + 1 none 2 ld rd, - y load indirect and pre-dec. y y - 1, rd (y) none 2 ldd rd,y+q load indirect with displacement rd (y + q) none 2 ld rd, z load indirect rd (z) none 2 ld rd, z+ load indirect and post-inc. rd (z), z z+1 none 2 ld rd, -z load indirect and pre-dec. z z - 1, rd (z) none 2 ldd rd, z+q load indirect with displacement rd (z + q) none 2 lds rd, k load direct from sram rd (k) none 2 st x, rr store indirect (x) rr none 2 st x+, rr store indirect and post-inc. (x) rr, x x + 1 none 2 st - x, rr store indirect and pre-dec. x x - 1, (x) rr none 2 st y, rr store indirect (y) rr none 2 st y+, rr store indirect and post-inc. (y) rr, y y + 1 none 2 st - y, rr store indirect and pre-dec. y y - 1, (y) rr none 2 std y+q,rr store indirect with displacement (y + q) rr none 2 st z, rr store indirect (z) rr none 2 st z+, rr store indirect and post-inc. (z) rr, z z + 1 none 2 st -z, rr store indirect and pre-dec. z z - 1, (z) rr none 2 std z+q,rr store indirect with displacement (z + q) rr none 2 sts k, rr store direct to sram (k) rr none 2 lpm load program memory r0 (z) none 3 lpm rd, z load program memory rd (z) none 3 lpm rd, z+ load program memory and post-inc rd (z), z z+1 none 3 spm store program memory (z) r1:r0 none - in rd, p in port rd pnone1 out p, rr out port p rr none 1 push rr push register on stack stack rr none 2 pop rd pop register from stack rd stack none 2 mcu control instructions nop no operation none 1 sleep sleep (see specific descr. for sleep function) none 1 wdr watchdog reset (see specific descr. for wdr/timer) none 1 break break for on-chip debug only none n/a mnemonics operands description operation flags #clocks 259 8246b?avr?09/11 attiny2313a/4313 26. ordering information notes: 1. for speed vs. supply voltage, see section 22.3 ?speed? on page 200 . 2. all packages are pb-free, halide-free and fully green, and th ey comply with the european directive for restriction of hazard- ous substances (rohs). 3. code indicators: ? h: nipdau lead finish ? u or n: matte tin ? r: tape & reel 4. can also be supplied in wafer form. contact your local atme l sales office for ordering information and minimum quantities. 5. nipdau finish 6. topside markings : ? 1st line: t2313 ? 2nd line: axx ? 3rd line: xxx 26.1 attiny2313a speed (mhz) (1) supply voltage (v) temperature range package (2) ordering code (3) 20 1.8 ? 5.5 industrial (-40 c to +85 c) (4) 20p3 attiny2313a-pu 20s attiny2313a-su attiny2313a-sur 20m1 attiny2313a-mu attiny2313a-mur 20m2 (5)(6) attiny2313a-mmh attiny2313a-mmhr package type 20p3 20-lead, 0.300" wide, plastic dual inline package (pdip) 20s 20-lead, 0.300" wide, plastic gull wing small outline package (soic) 20m1 20-pad, 4 x 4 x 0.8 mm body, quad flat no-lead / micro lead frame package (mlf) 20m2 20-pad, 3 x 3 x 0.85 mm body, very thin quad flat no lead package (vqfn) 260 8246b?avr?09/11 attiny2313a/4313 notes: 1. for speed vs. supply voltage, see section 22.3 ?speed? on page 200 . 2. all packages are pb-free, halide-free and fully green, and th ey comply with the european directive for restriction of hazard- ous substances (rohs). 3. code indicators: ? h: nipdau lead finish ? u or n: matte tin ? r: tape & reel 4. can also be supplied in wafer form. contact your local atme l sales office for ordering information and minimum quantities. 5. nipdau finish 6. topside markings: ? 1st line: t4313 ? 2nd line: axx ? 3rd line: xxx 26.2 attiny4313 speed (mhz) (1) supply voltage (v) temperature range package (2) ordering code (3) 20 1.8 ? 5.5 industrial (-40 c to +85 c) (4) 20p3 attiny4313-pu 20s attiny4313-su attiny4313-sur 20m1 attiny4313-mu attiny4313-mur 20m2 (5)(6) attiny4313-mmh attiny4313-mmhr package type 20p3 20-lead, 0.300" wide, plastic dual inline package (pdip) 20s 20-lead, 0.300" wide, plastic gull wing small outline package (soic) 20m1 20-pad, 4 x 4 x 0.8 mm body, quad flat no-lead/micro lead frame package (mlf) 20m2 20-pad, 3 x 3 x 0.85 mm body, very thin quad flat no lead package (vqfn) 261 8246b?avr?09/11 attiny2313a/4313 27. packaging information 27.1 20p3 2 3 25 orch a rd p a rkw a y sa n jo s e, ca 951 3 1 title drawing no. r rev. 20p 3 , 20-le a d (0. 3 00"/7.62 mm wide) pl as tic d ua l inline p a ck a ge (pdip) d 20p 3 2010-10-19 pin 1 e1 a1 b e b1 c l s eating plane a d e eb ec common dimen s ion s (unit of me asu re = mm) s ymbol min nom max note a ? ? 5. 33 4 a1 0. 38 1 ? ? d 25.49 3 ? 25.9 8 4 note 2 e 7.620 ? 8 .255 e1 6.096 ? 7.112 note 2 b 0. 3 56 ? 0.559 b1 1.270 ? 1.551 l 2.921 ? 3 . 8 10 c 0.20 3 ? 0. 3 56 eb ? ? 10.922 ec 0.000 ? 1.524 e 2.540 typ note s : 1. thi s p a ck a ge conform s to jedec reference m s -001, v a ri a tion ad. 2. dimen s ion s d a nd e1 do not incl u de mold fl as h or protr us ion. mold fl as h or protr us ion s h a ll not exceed 0.25 mm (0.010"). 262 8246b?avr?09/11 attiny2313a/4313 27.2 20s 263 8246b?avr?09/11 attiny2313a/4313 27.3 20m1 2325 orchard parkway san jose, ca 95131 title drawing no. r rev. 20m1 , 20-pad, 4 x 4 x 0.8 mm body, lead pitch 0.50 mm, a 20m1 10/27/04 2.6 mm exposed pad, micro lead frame package (mlf) a 0.70 0.75 0.80 a1 ? 0.01 0.05 a2 0.20 ref b 0.18 0.23 0.30 d 4.00 bsc d2 2.45 2.60 2.75 e 4.00 bsc e2 2.45 2.60 2.75 e 0.50 bsc l 0.35 0.40 0.55 side view pin 1 id pin #1 notch (0.20 r) bottom view top view note: reference jedec standard mo-220, fig . 1 (saw singulation) wggd-5. common dimensions (unit of measure = mm) symbol min nom max note d e e a2 a1 a d2 e2 0.08 c l 1 2 3 b 1 2 3 264 8246b?avr?09/11 attiny2313a/4313 27.4 20m2 title drawing no. gpc rev. packa g e drawin g contact: p a ck a gedr a wing s @ a tmel.com 20m2 zfc b 20m2, 20-pad, 3 x 3 x 0.85 mm body, lead pitch 0.45 mm, 1.55 x 1.55 mm exposed pad, thermally enhanced plastic very thin quad flat no lead package (vqfn) 10/24/0 8 15 14 1 3 12 11 1 2 3 4 5 16 17 1 8 19 20 10 9 8 7 6 d2 e2 e b k l pin #1 ch a mfer (c 0. 3 ) d e s ide view a1 y pin 1 id bottom view top view a1 a c c0.1 8 ( 8 x) 0. 3 ref (4x) common dimen s ion s (unit of me asu re = mm) s ymbol min nom max note a 0.75 0. 8 0 0. 8 5 a1 0.00 0.02 0.05 b 0.17 0.22 0.27 c 0.152 d 2.90 3 .00 3 .10 d2 1.40 1.55 1.70 e 2.90 3 .00 3 .10 e2 1.40 1.55 1.70 e ? 0.45 ? l 0. 3 5 0.40 0.45 k 0.20 ? ? y 0.00 ? 0.0 8 265 8246b?avr?09/11 attiny2313a/4313 28. errata the revision letters in this section refer to the revision of the corresponding attiny2313a/4313 device. 28.1 attiny2313a 28.1.1 rev. d no known errata. 28.1.2 rev. a ? c these device revisions were referred to as attiny2313/attiny2313v. 28.2 attiny4313 28.2.1 rev. a no known errata. 266 8246b?avr?09/11 attiny2313a/4313 29. datasheet revision history 29.1 rev. 8246b ? 10/11 1. updated device status from preliminary to final. 2. updated document template. 3. added order codes for tape&reel devices, on page 259 and page 260 4. updated figures: ? figure 23-33 on page 223 ? figure 23-44 on page 228 ? figure 23-81 on page 247 ? figure 23-92 on page 252 5. updated sections: ? section 5. ?memories? on page 16 ? section 19. ?self-programming? on page 173 ? section 20. ?lock bits, fuse bits and device signature? on page 178 ? section 21. ?external programming? on page 184 ? section 26. ?ordering information? on page 259 29.2 rev. 8246a ? 11/09 1. initial revision. created from document 2543_t2313. 2. updated datasheet template. 3. added vqfn in the pinout figure 1-1 on page 2 . 4. added section 7.2 ?software bod disable? on page 35 . 5. added section 7.3 ?power reduction register? on page 35 . 6. updated table 7-2, ?sleep mode select,? on page 37 . 7. added section 7.5.3 ?bodcr ? brown-out detector control register? on page 38 . 8. added reset disable function in figure 8-1 on page 39 . 9. added pin change interrupts pcint1 and pcint2 in table 9-1 on page 48 . 10. added pcint17..8 and pcmsk2..1 in section 9.2 ?external interrupts? on page 49 . 11. added section 9.3.4 ?pcmsk2 ? pin change mask register 2? on page 53 . 12. added section 9.3.5 ?pcmsk1 ? pin change mask register 1? on page 54 . 13. updated section 10.2.1 ?alternate functions of port a? on page 62 . 14. updated section 10.2.2 ?alternate functions of port b? on page 63 . 15. updated section 10.2.3 ?alternate functions of port d? on page 67 . 16. added umsel1 and umsel0 in section 14.10.4 ?ucsrc ? usart control and sta- tus register c? on page 140 . 17. added section 15. ?usart in spi mode? on page 146 . 18. added usi buffer register (usibr) in section 16.2 ?overview? on page 156 and in fig- ure 16-1 on page 156 . 19. added section 16.5.4 ?usibr ? usi buffer register? on page 167 . 20. updated section 19.6.3 ?reading device signature imprint table from firmware? on page 175 . 267 8246b?avr?09/11 attiny2313a/4313 21. updated section 19.7.1 ?spmcsr ? store program memory control and status regis- ter? on page 176 . 22. added section 20.3 ?device signature imprint table? on page 180 . 23. updated section 20.3.1 ?calibration byte? on page 181 . 24. changed bs to bs1 in section 20.6.13 ?reading the signature bytes? on page 189 . 25. updated section 22.2 ?dc characteristics? on page 198 . 26. added section 23.1 ?effect of power reduction? on page 206 . 27. updated characteristic plots in section 23. ?typical characteristics? for attiny2313a (pages 207 - 230 ), and added plots for attiny4313 (pages 231 - 254 ). 28. updated section 24. ?register summary? on page 255 . 29. updated section 26. ?ordering information? on page 259 , added the package type 20m2 and the ordering code -mmh (vqfn), and added the topside marking note. 268 8246b?avr?09/11 attiny2313a/4313 i 8246b?avr?09/11 attiny2313a/4313 table of contents features ................ ................ .............. ............... .............. .............. ............ 1 1 pin configurations ..... ................ ................. ................ ................. ............ 2 1.1 pin descriptions .................................................................................................3 2 overview ............ ................ ................ ............... .............. .............. ............ 5 2.1 block diagram ...................................................................................................5 2.2 comparison between attiny2313a and attiny4313 ........................................6 3 about ............. ................ ................. ................ ................. .............. ............ 7 3.1 resources .........................................................................................................7 3.2 code examples .................................................................................................7 3.3 data retention ...................................................................................................7 4cpu core ............... .............. .............. ............... .............. .............. ............ 8 4.1 architectural overview .......................................................................................8 4.2 alu ? arithmetic logic unit ...............................................................................9 4.3 status register ..................................................................................................9 4.4 general purpose register file ........................................................................10 4.5 stack pointer ...................................................................................................12 4.6 instruction execution timing ...........................................................................12 4.7 reset and interrupt handling ...........................................................................13 5 memories ............... .............. .............. ............... .............. .............. .......... 15 5.1 program memory (flash) .................................................................................15 5.2 data memory (sram) and register files .......................................................16 5.3 data memory (eeprom) ................................................................................17 5.4 register description ........................................................................................22 6 clock system ........... ................ ................ ................. ................ ............. 25 6.1 clock subsystems ...........................................................................................25 6.2 clock sources .................................................................................................26 6.3 system clock prescaler ..................................................................................30 6.4 clock output buffer .........................................................................................31 6.5 register description ........................................................................................31 7 power management and sleep mo des ............... .............. ............ ........ 33 7.1 sleep modes ....................................................................................................33 7.2 software bod disable .....................................................................................34 ii 8246b?avr?09/11 attiny2313a/4313 7.3 power reduction register ...............................................................................34 7.4 minimizing power consumption ......................................................................35 7.5 register description ........................................................................................36 8 system control and reset ...... ................ ................. ................ ............. 38 8.1 resetting the avr ...........................................................................................38 8.2 reset sources .................................................................................................39 8.3 internal voltage reference ..............................................................................41 8.4 watchdog timer ..............................................................................................41 8.5 register description ........................................................................................44 9 interrupts ........ ................. ................ ................. .............. .............. .......... 47 9.1 interrupt vectors ..............................................................................................47 9.2 external interrupts ...........................................................................................48 9.3 register description ........................................................................................50 10 i/o-ports ........ ................ ................. ................ ................. .............. .......... 54 10.1 ports as general digital i/o .............................................................................55 10.2 alternate port functions ..................................................................................59 10.3 register description ........................................................................................68 11 8-bit timer/counter0 with pw m .............. ................. ................ ............. 70 11.1 features ..........................................................................................................70 11.2 overview ..........................................................................................................70 11.3 clock sources .................................................................................................71 11.4 counter unit ....................................................................................................71 11.5 output compare unit .......................................................................................72 11.6 compare match output unit ............................................................................74 11.7 modes of operation .........................................................................................75 11.8 timer/counter timing diagrams .....................................................................79 11.9 register description ........................................................................................81 12 16-bit timer/counter1 ......... .............. ............... .............. .............. .......... 88 12.1 features ..........................................................................................................88 12.2 overview ..........................................................................................................88 12.3 timer/counter clock sources .........................................................................90 12.4 counter unit ....................................................................................................90 12.5 input capture unit ...........................................................................................91 12.6 output compare units .....................................................................................93 iii 8246b?avr?09/11 attiny2313a/4313 12.7 compare match output unit ............................................................................95 12.8 modes of operation .........................................................................................96 12.9 timer/counter timing diagrams ...................................................................104 12.10 accessing 16-bit registers ............................................................................106 12.11 register description ......................................................................................110 13 timer/counter0 and time r/counter1 prescalers ..... .............. ........... 117 13.1 internal clock source ....................................................................................117 13.2 prescaler reset .............................................................................................117 13.3 external clock source ...................................................................................117 13.4 register description ......................................................................................118 14 usart ............. ................. ................ .............. .............. .............. ........... 119 14.1 features ........................................................................................................119 14.2 overview ........................................................................................................119 14.3 clock generation ...........................................................................................120 14.4 frame formats ..............................................................................................123 14.5 usart initialization .......................................................................................124 14.6 data transmission ? the usart transmitter ..............................................125 14.7 data reception ? the usart receiver .......................................................129 14.8 asynchronous data reception ......................................................................132 14.9 multi-processor communication mode ..........................................................135 14.10 register description ......................................................................................136 14.11 examples of baud rate setting .....................................................................141 15 usart in spi mode .......... .............. .............. .............. .............. ........... 145 15.1 features ........................................................................................................145 15.2 overview ........................................................................................................145 15.3 clock generation ...........................................................................................145 15.4 spi data modes and timing ..........................................................................146 15.5 frame formats ..............................................................................................147 15.6 data transfer .................................................................................................149 15.7 avr usart mspim vs. avr spi ................................................................151 15.8 register description ......................................................................................152 16 usi ? universal seri al interface ............ ................. ................ ............. 155 16.1 features ........................................................................................................155 16.2 overview ........................................................................................................155 16.3 functional descriptions .................................................................................156 iv 8246b?avr?09/11 attiny2313a/4313 16.4 alternative usi usage ...................................................................................162 16.5 register description ......................................................................................162 17 analog comparator .......... .............. .............. .............. .............. ........... 167 17.1 register description ......................................................................................167 18 debugwire on-chip debug s ystem .............. .............. .............. ........ 169 18.1 features ........................................................................................................169 18.2 overview ........................................................................................................169 18.3 physical interface ..........................................................................................169 18.4 software break points ...................................................................................170 18.5 limitations of debugwire .............................................................................170 18.6 register description ......................................................................................171 19 self-programming ...... ................ ................. ................ .............. ........... 172 19.1 features ........................................................................................................172 19.2 overview ........................................................................................................172 19.3 lock bits ........................................................................................................172 19.4 self-programming the flash ..........................................................................172 19.5 preventing flash corruption ..........................................................................175 19.6 programming time for flash when using spm ............................................175 19.7 register description ......................................................................................175 20 lock bits, fuse bits and device signature .......... ................ ............. 177 20.1 lock bits ........................................................................................................177 20.2 fuse bits ........................................................................................................178 20.3 device signature imprint table .....................................................................179 20.4 reading lock bits, fuse bits and signature data from software .................180 21 external programming ....... .............. ............... .............. .............. ........ 183 21.1 memory parametrics .....................................................................................183 21.2 parallel programming ....................................................................................183 21.3 serial programming .......................................................................................192 21.4 programming time for flash and eeprom ................ ............ ............. ........196 22 electrical characteristics ... .............. ............... .............. .............. ........ 198 22.1 absolute maximum ratings* .........................................................................198 22.2 dc characteristics .........................................................................................198 22.3 speed ............................................................................................................199 22.4 clock characteristics .....................................................................................200 v 8246b?avr?09/11 attiny2313a/4313 22.5 system and reset characteristics ................................................................201 22.6 analog comparator characteristics ...............................................................202 22.7 parallel programming characteristics ...........................................................203 22.8 serial programming characteristics ..............................................................205 23 typical characteristics ....... .............. ............... .............. .............. ........ 206 23.1 effect of power reduction .............................................................................206 23.2 attiny2313a ..................................................................................................207 23.3 attiny4313 ....................................................................................................231 24 register summary ............ .............. .............. .............. .............. ........... 255 25 instruction set summary ... .............. ............... .............. .............. ........ 257 26 ordering information .......... .............. ............... .............. .............. ........ 259 26.1 attiny2313a ..................................................................................................259 26.2 attiny4313 ....................................................................................................260 27 packaging information .......... ................ ................. ................ ............. 261 27.1 20p3 ..............................................................................................................261 27.2 20s ................................................................................................................262 27.3 20m1 ..............................................................................................................263 27.4 20m2 ..............................................................................................................264 28 errata ........... ................ ................ ................. ................ .............. ........... 265 28.1 attiny2313a ..................................................................................................265 28.2 attiny4313 ....................................................................................................265 29 datasheet revision history .. ................ ................. ................ ............. 266 29.1 rev. 8246b ? 10/11 .......................................................................................266 29.2 rev. 8246a ? 11/09 .......................................................................................266 8246b?avr?09/11 headquarters international atmel corporation 2325 orchard parkway san jose, ca 95131 usa tel: 1(408) 441-0311 fax: 1(408) 487-2600 atmel asia limited unit 01-5 & 16, 19/f bea tower, millennium city 5 418 kwun tong road kwun tong, kowloon hong kong tel: (852) 2245-6100 fax: (852) 2722-1369 atmel munich gmbh business campus parkring 4 d-85748 garching b. munich germany tel: (+49) 89-31970-0 fax: (+49) 89-3194621 atmel japan 9f, tonetsu shinkawa bldg. 1-24-8 shinkawa chuo-ku, tokyo 104-0033 japan tel: (81) 3-3523-3551 fax: (81) 3-3523-7581 product contact web site www.atmel.com technical support avr@atmel.com sales contact www.atmel.com/contacts literature requests www.atmel.com/literature disclaimer: the information in this document is provided in connection with atmel products. no license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of atmel products. except as set forth in atmel?s terms and condi- tions of sale located on atmel?s web site, atmel assumes no li ability whatsoever and disclaims any express, implied or statutor y warranty relating to its products including, but not limited to, the implied warranty of merchantability, fitness for a particu lar purpose, or non-infringement. in no event shall atmel be liable for any direct, indirect, consequential, punitive, special or i nciden- tal damages (including, without limitation, damages for loss of profits, business interruption, or loss of information) arising out of the use or inability to use this document, even if atme l has been advised of the possibility of such damages. atmel makes no representations or warranties with respect to the accuracy or comp leteness of the contents of this document and reserves the rig ht to make changes to specifications and product descriptions at any time without notice. atmel does not make any commitment to update the information contained her ein. unless specifically provided otherwise, atmel products are not suitable for, and shall not be used in, automotive applications. atmel?s products are not int ended, authorized, or warranted for use as components in applications in tended to support or sustain life. ? 2011 atmel corporation. all rights reserved. atmel ? , logo and combinations thereof, avr ? and others are registered trademarks or trade- marks of atmel corporation or its subsidiaries. other terms and product names may be trademarks of others. |
Price & Availability of TSC80C31-36AXR
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |